Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failure to find de.jflex:cup_runtime:jar:11b #390

Closed
ambs opened this issue Sep 29, 2018 · 9 comments
Closed

Failure to find de.jflex:cup_runtime:jar:11b #390

ambs opened this issue Sep 29, 2018 · 9 comments
Assignees
@lsf37
Labels
bug Not working as intended
Milestone
1.7.0

Comments

@ambs
Copy link

ambs commented Sep 29, 2018

Hi. I'm new to Java and all these new ways to automate builds. I am trying to build a simple project in IntelliJ IDEA. I configured Maven as described in the documentation. Nevertheless, when running the compile step, I get

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal de.jflex:jflex-maven-plugin:1.7.0:generate (default) on project pt-flex: Execution default of goal de.jflex:jflex-maven-plugin:1.7.0:generate failed: Plugin de.jflex:jflex-maven-plugin:1.7.0 or one of its dependencies could not be resolved: Failure to find de.jflex:cup_runtime:jar:11b in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

Any help is welcome.
@regisd regisd added this to the 1.7.0 milestone Sep 29, 2018
@regisd regisd added the bug Not working as intended label Sep 29, 2018
@regisd
Copy link
Member

regisd commented Sep 29, 2018 •
edited
Loading

@lsf37 we haven't publish de.jflex:cup_runtime. I don't have permissions to do this, so I'm afraid this issue falls on you.

@regisd
Copy link
Member

regisd commented Sep 29, 2018 •
edited
Loading

@ambs Thanks a lot for reporting the problem! Our mistake: We didn't deploy one of our internal dependency.

I see two options to use JFlex on your project

  • use jflex version 1.6.1 (instead 1.7.0) until this bug is fixed, i.e. use 
     <dependency>
    <groupId>de.jflex</groupId>
    <artifactId>jflex</artifactId>
    <version>1.6.1</version>
 </dependency>
  • install jflex from sources: 
      git clone --branch v1.7.0 --depth 1 https://github.com/jflex-de/jflex.git 
  cd jflex
  ./mvnw install

@regisd regisd changed the title Maven dependency problem Failure to find de.jflex:cup_runtime:jar:11b Sep 30, 2018
@ambs
Copy link
Author

ambs commented Sep 30, 2018 •
edited
Loading

Thanks. Will try 1.6.1 for now, as it is easier to explain to students.

In fact, this opens another set of problems:

[ERROR] Source option 5 is no longer supported. Use 6 or later.
[ERROR] Target option 1.5 is no longer supported. Use 1.6 or later.

@regisd
Copy link
Member

regisd commented Oct 1, 2018 •
edited
Loading

@ambs Let's follow-up this java issue in #400

@regisd regisd closed this as completed Oct 1, 2018
@regisd regisd reopened this Oct 1, 2018
@regisd regisd mentioned this issue Oct 1, 2018
Merged
regisd added a commit that referenced this issue Oct 2, 2018
@regisd
Create jflex rule for bazel (#401)
ec9c51a 
* Define the Bazel rule `jflex`. Fix #204 (Bazel support)
  - **N.B.** The rule uses JFlex 1.6.1 because v1.7.0 has missing dependencies (see #390)

* Show how to use the rule on example "simple"
  - Make `examples` a Bazel workspace
  - In an wish to support all build systems in the examples, show how to generate a lexer with Bazel on "simple".
  - Attempted to have a **java_test** on `Yylex`. However dropped, because the dump format has changed between 1.6.1 and 1.7.0. Blocked on #390 
  - Import the deps needed for **simple** via the bazel migration tool.
  - Also define, a few third_party aliases
  - **N.B.** Renamed ant build directory to **antbuild** because we cannot have both a `build` directory ant a `BUILD` file on case insensitive filesystems

* Add documentation

* Cache the bazel output & repo cache directories in Travis
@lsf37
Copy link
Member

lsf37 commented Oct 6, 2018

Sorry about all this, I'm looking into it now. It seems the pom file for cup explicitly tells it to skip deployment, but I guess that should only apply to cup itself and not the runtime.

@lsf37
Copy link
Member

lsf37 commented Oct 7, 2018

So, I've manually deployed cup_runtime and cup-parent 11b. For some reason maven still does not find cup-parent even though it does find and download the pom and the jar for cup_runtime.

Maybe it just needs some more time to sync, but why it would sync only one and not the other mystifies me. Will give it a bit more time.

@lsf37
Copy link
Member

lsf37 commented Oct 7, 2018

And now it's there and seems to work.

The reason I didn't catch this in my release testing is that maven caches things locally, which means all dependencies were present on my machine and it didn't try to download them.

@lsf37 lsf37 closed this as completed Oct 7, 2018
@lsf37 lsf37 mentioned this issue Oct 7, 2018
Merged
@regisd
Copy link
Member

regisd commented Oct 7, 2018

https://repo.maven.apache.org/maven2/de/jflex/cup_runtime/

@ulenkar
Copy link

ulenkar commented May 27, 2019

Just to let you know - I've just had the same problem and solved it by installing jflex from sources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lsf37 lsf37

Labels
bug Not working as intended
Projects
None yet
Milestone
1.7.0
Development

No branches or pull requests
4 participants
@ambs @regisd @lsf37 @ulenkar