Maven 1

Missing plugins\plugin-parent-1.0\plugin.jelly in bootstrap build

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.0-rc3
  • Fix Version/s: 1.0-rc3
  • Component/s: core
  • Labels:
    None
  • Number of attachments :
    0

Description

When doing a build-bootstrap I get the following error.

[echo]
[echo] |
[echo] | BUILDING MAVEN WITH ITSELF...
[echo] |
[echo]
[exec] __ __
[exec] | \/ |__ Apache_ ___
[exec] | |\/| / ` \ V / -) ' \ ~ intelligent projects ~
[exec] || |_,|_/__|||_| v. 1.0-rc3-SNAPSHOT

[exec] plugin license is cached (dynatag dep) but no longer present
[exec] Cache invalidated due to out of date plugins
[exec] org.apache.maven.MavenException: Error reading plugin script
[exec] at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptH
ousing.java:180)
[exec] at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(Plu
ginManager.java:203)
[exec] at org.apache.maven.plugin.PluginManager.initialize(PluginManage
r.java:255)
[exec] at org.apache.maven.MavenSession.initializePluginManager(MavenSe
ssion.java:207)
[exec] at org.apache.maven.MavenSession.initialize(MavenSession.java:17
4)
[exec] at org.apache.maven.cli.App.doMain(App.java:472)
[exec] at org.apache.maven.cli.App.main(App.java:1214)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at com.werken.forehead.Forehead.run(Forehead.java:551)
[exec] at com.werken.forehead.Forehead.main(Forehead.java:581)
[exec] — Nested Exception —
[exec] java.io.FileNotFoundException: C:\Documents and Settings\trajano\.ma
ven\plugins\plugin-parent-1.0\plugin.jelly (The system cannot find the file spec
ified)
[exec] at java.io.FileInputStream.open(Native Method)
[exec] at java.io.FileInputStream.<init>(FileInputStream.java:106)
[exec] at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptH
ousing.java:176)
[exec] at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(Plu
ginManager.java:203)
[exec] at org.apache.maven.plugin.PluginManager.initialize(PluginManage
r.java:255)
[exec] at org.apache.maven.MavenSession.initializePluginManager(MavenSe
ssion.java:207)
[exec] at org.apache.maven.MavenSession.initialize(MavenSession.java:17
4)
[exec] at org.apache.maven.cli.App.doMain(App.java:472)

[exec] at org.apache.maven.cli.App.main(App.java:1214)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at com.werken.forehead.Forehead.run(Forehead.java:551)
[exec] at com.werken.forehead.Forehead.main(Forehead.java:581)
[exec] You have encountered an unknown error running Maven. Please help us
to correct
[exec] this problem by following these simple steps:
[exec] - read the Maven FAQ at http://maven.apache.org/faq.html
[exec] - run the same command again with the '-e' parameter, eg maven -e ja
r
[exec] - search the maven-user archives for the error at
[exec] http://nagoya.apache.org/eyebrowse/SummarizeList?listName=users@mave
n.apache.org
[exec] - post the output of maven -e to JIRA at
[exec] http://jira.codehaus.org/BrowseProject.jspa?id=10030 (you must sign
up first)
[exec] - run 'maven --info' and post the output as the environment to the b
ug above

Checking the maven-plugins/plugin-parent project I only see

8 .cvsignore
1,403 project.properties
5,670 project.xml
264 README.txt

no plugin.jelly

Perhaps someone forgot to commit that code?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Massol added a comment -

No. It simply means that you have not done a CVS update of your maven/ 1.0 branch module. If you do this, you'll find that the build will properly exclude the plugin-parent/ directory which is not a plugin...

Show
Vincent Massol added a comment - No. It simply means that you have not done a CVS update of your maven/ 1.0 branch module. If you do this, you'll find that the build will properly exclude the plugin-parent/ directory which is not a plugin...
Hide
Permalink
Archimedes Trajano added a comment -

I think I am working on the HEAD branch, does this mean that HEAD will not compile anymore? Anyway, I have put in an additional file plugin.jelly in the plugin-parent project which has only one line

<project />

And now bootstrap on the HEAD branch works now.

Show
Archimedes Trajano added a comment - I think I am working on the HEAD branch, does this mean that HEAD will not compile anymore? Anyway, I have put in an additional file plugin.jelly in the plugin-parent project which has only one line <project /> And now bootstrap on the HEAD branch works now.
Hide
Permalink
Archimedes Trajano added a comment -

I cannot add any files into the issue, but like I said its just one file that needs to be added into the directory to fix the issue.

Show
Archimedes Trajano added a comment - I cannot add any files into the issue, but like I said its just one file that needs to be added into the directory to fix the issue.
Hide
Permalink
Vincent Massol added a comment -

Sorry but I don't think you are working with HEAD for the reason that your option says that you're working with "1.0-rc3-SNAPSHOT"! But you should know better than me what you're doing...

Also, your "fix" is not right. Please, whether you are working with HEAD or with the 1.0 branch, simply do a CVS update and it'll fix the problem.

Thanks

Show
Vincent Massol added a comment - Sorry but I don't think you are working with HEAD for the reason that your option says that you're working with "1.0-rc3-SNAPSHOT"! But you should know better than me what you're doing... Also, your "fix" is not right. Please, whether you are working with HEAD or with the 1.0 branch, simply do a CVS update and it'll fix the problem. Thanks
Hide
Permalink
Archimedes Trajano added a comment -

Thanks, you're right about the 1.0 tag, I must've missed that one. So probably it failed because my plugins was in HEAD but the maven tree was in 1.0.

My bad, thanks. Now I get a different issue.

[echo]
[echo] |
[echo] | BUILDING MAVEN WITH ITSELF...
[echo] |
[echo]
[exec] __ __
[exec] | \/ |__ Apache_ ___
[exec] | |\/| / ` \ V / -) ' \ ~ intelligent projects ~
[exec] || |_,|_/__|||_| v. 1.1-SNAPSHOT

[exec] java.io.FileNotFoundException: C:\Documents and Settings\trajano\.ma
ven\plugins\clean\project.xml (The system cannot find the path specified)
[exec] at java.io.FileInputStream.open(Native Method)
[exec] at java.io.FileInputStream.<init>(FileInputStream.java:106)
[exec] at org.apache.commons.digester.Digester.parse(Digester.java:1525
)
[exec] at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.jav
a:183)
[exec] at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144)
[exec] at org.apache.maven.plugin.JellyScriptHousing.getProject(JellySc
riptHousing.java:97)
[exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginMa
nager.java:572)
[exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManag
er.java:523)
[exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:2
65)
[exec] Total time: 26 seconds
[exec] at org.apache.maven.cli.App.doMain(App.java:466)
[exec] at org.apache.maven.cli.App.main(App.java:1117)
[exec] Finished at: Tue May 04 17:02:18 CEST 2004

[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at com.werken.forehead.Forehead.run(Forehead.java:551)
[exec] at com.werken.forehead.Forehead.main(Forehead.java:581)

Show
Archimedes Trajano added a comment - Thanks, you're right about the 1.0 tag, I must've missed that one. So probably it failed because my plugins was in HEAD but the maven tree was in 1.0. My bad, thanks. Now I get a different issue. [echo] [echo] | [echo] | BUILDING MAVEN WITH ITSELF... [echo] | [echo] [exec] __ __ [exec] | \/ |__ Apache_ ___ [exec] | |\/| / ` \ V / -) ' \ ~ intelligent projects ~ [exec] || |_,|_/__|||_| v. 1.1-SNAPSHOT [exec] java.io.FileNotFoundException: C:\Documents and Settings\trajano\.ma ven\plugins\clean\project.xml (The system cannot find the path specified) [exec] at java.io.FileInputStream.open(Native Method) [exec] at java.io.FileInputStream.<init>(FileInputStream.java:106) [exec] at org.apache.commons.digester.Digester.parse(Digester.java:1525 ) [exec] at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.jav a:183) [exec] at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) [exec] at org.apache.maven.plugin.JellyScriptHousing.getProject(JellySc riptHousing.java:97) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginMa nager.java:572) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManag er.java:523) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:2 65) [exec] Total time: 26 seconds [exec] at org.apache.maven.cli.App.doMain(App.java:466) [exec] at org.apache.maven.cli.App.main(App.java:1117) [exec] Finished at: Tue May 04 17:02:18 CEST 2004 [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581)
Hide
Permalink
Archimedes Trajano added a comment -

BTW the error above was with HEAD on maven and HEAD on plugins.

There is no MAVEN_1_0-BRANCH tag on maven-plugins

C:\Projects\maven-plugins2>cvs log project.xml | more

RCS file: /home/cvspublic/maven-plugins/project.xml,v
Working file: project.xml
head: 1.19
branch:
locks: strict
access list:
symbolic names:
MAVEN_RC1_REFACTOR: 1.4.0.6
MAVEN_POST_RC1_REFACTOR: 1.4
MAVEN_RC1_STABLE: 1.4.0.4
BRW_TEST: 1.4.0.2
MAVEN_PRE_RC1_REFACTOR: 1.4
MAVEN_1_0_B10: 1.4
MAVEN_1_0_B9: 1.3
MAVEN_1_0_B8: 1.1.1.1
PLUGINS_REWORK: 1.1.1.1
jakarta: 1.1.1
keyword substitution: kv
total revisions: 20; selected revisions: 20
description:

Show
Archimedes Trajano added a comment - BTW the error above was with HEAD on maven and HEAD on plugins. There is no MAVEN_1_0-BRANCH tag on maven-plugins C:\Projects\maven-plugins2>cvs log project.xml | more RCS file: /home/cvspublic/maven-plugins/project.xml,v Working file: project.xml head: 1.19 branch: locks: strict access list: symbolic names: MAVEN_RC1_REFACTOR: 1.4.0.6 MAVEN_POST_RC1_REFACTOR: 1.4 MAVEN_RC1_STABLE: 1.4.0.4 BRW_TEST: 1.4.0.2 MAVEN_PRE_RC1_REFACTOR: 1.4 MAVEN_1_0_B10: 1.4 MAVEN_1_0_B9: 1.3 MAVEN_1_0_B8: 1.1.1.1 PLUGINS_REWORK: 1.1.1.1 jakarta: 1.1.1 keyword substitution: kv total revisions: 20; selected revisions: 20 description:
Hide
Permalink
Archimedes Trajano added a comment -

Dang, forgot to specify, this was a clean checkout, I moved the previous checked out modules (maven/maven-plugins) out of the way and checked them out again from scratch.

Show
Archimedes Trajano added a comment - Dang, forgot to specify, this was a clean checkout, I moved the previous checked out modules (maven/maven-plugins) out of the way and checked them out again from scratch.
Hide
Permalink
Vincent Massol added a comment -

The last error you're getting on HEAD is "normal". HEAD is not stable and is not currently meant to be built. I'd highly suggest you to use the 1.0 branch of maven/.

Show
Vincent Massol added a comment - The last error you're getting on HEAD is "normal". HEAD is not stable and is not currently meant to be built. I'd highly suggest you to use the 1.0 branch of maven/.
Hide
Permalink
Archimedes Trajano added a comment -

I take it that "normal" occurence is a known bug already.

Okay I am checking out using on the main branch, clean copy again.

cvs -z9 -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co -P -r
MAVEN-1_0-BRANCH maven

I am leaving plugins with HEAD branch since I do not see any branch for it that looks like MAVEN-1_0-BRANCH

and yes it works! Thanks.

Show
Archimedes Trajano added a comment - I take it that "normal" occurence is a known bug already. Okay I am checking out using on the main branch, clean copy again. cvs -z9 -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co -P -r MAVEN-1_0-BRANCH maven I am leaving plugins with HEAD branch since I do not see any branch for it that looks like MAVEN-1_0-BRANCH and yes it works! Thanks.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.