[jira] Commented: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set
The following comment has been added to this issue: Author: Håvard Bjåstad Created: Thu, 21 Oct 2004 3:16 AM Body: I'd like to tack on to this one, even though my problem is with reactor (not multiproject). We have a J2EE project with several sub-projects, each building their own artifact. When running the reactor to build all sub-projects before they are included in the main project's EAR file, maven first looks for deployed jars. This doesn't make sense, as the reactor's job is to build the jars for all sub-projects! As mentioned above, I think the dependencies should be ignored on startup, if they are included in the reactor build. - View this comment: http://jira.codehaus.org/browse/MAVEN-1270?page=comments#action_25639 - View the issue: http://jira.codehaus.org/browse/MAVEN-1270 Here is an overview of the issue: - Key: MAVEN-1270 Summary: multiproject:clean fails due to dependencies in reactor set Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Versions: 1.0-rc2 Assignee: Reporter: Cameron Fieber Created: Wed, 5 May 2004 2:18 PM Updated: Thu, 21 Oct 2004 3:16 AM Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2 Description: I appologize if this is already entered, but I was unable to find it searching JIRA. This is the same as or similar to #MAVEN-443 which was marked as can't reproduce. If you have a multiproject build, you can't execute clean until all artifacts in that build that depend on other artifacts in the build have been produced. The ideal behaviour of multiproject:clean would be to either ignore dependencies not needed for the clean task itself, or consider a dependency satisfied if it is in the reactor set. The case where this feature would be a particular benefit is when you have an existing source tree, which has been built, and a new component is added. If you do an update and pulling down the new component it has yet to be compiled. You then can't do multiproject:clean on your existing tree because the new dependencies to the new component can't be resolved. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1474) exceptions writing classes that use DOM
The following comment has been added to this issue:
Author: Malachi de AElfweald
Created: Thu, 21 Oct 2004 2:17 PM
Body:
I thought the problem would be something like that, just wasn't sure how to fix it.
Your suggestion did work. Thanks.
-
View this comment:
http://jira.codehaus.org/browse/MAVEN-1474?page=comments#action_25660
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1474
Here is an overview of the issue:
-
Key: MAVEN-1474
Summary: exceptions writing classes that use DOM
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0
Assignee:
Reporter: Malachi de AElfweald
Created: Wed, 20 Oct 2004 5:12 PM
Updated: Thu, 21 Oct 2004 2:17 PM
Environment: WinXPSP2, JDK/J2SE 1.5/5.0
Description:
When compiling without Maven, everything works fine.
When compiling with Maven, it says that getTextContent and setTextContent (DOM) are
not found.
maven.compile.source=1.5
maven.compile.target=1.5
java:compile:
[echo] Compiling to E:\devel\excp/target/classes
[javac] Compiling 13 source files to E:\devel\excp\target\classes
E:\devel\excp\src\java\org\eoti\tools\excp\cfg\DOMWrapper.java:108: cannot find symbol
symbol : method setTextContent(java.lang.String)
location: interface org.w3c.dom.Element
cp.setTextContent(url.toExternalForm());
^
E:\devel\excp\src\java\org\eoti\tools\excp\cfg\EXCPDomNode.java:57: cannot find symbol
symbol : method getTextContent()
location: interface org.w3c.dom.Node
public String getText(){return node.getTextContent().trim();}
^
2 errors
BUILD FAILED
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1474) exceptions writing classes that use DOM
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1474
Here is an overview of the issue:
-
Key: MAVEN-1474
Summary: exceptions writing classes that use DOM
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0
Assignee:
Reporter: Malachi de AElfweald
Created: Wed, 20 Oct 2004 5:12 PM
Updated: Thu, 21 Oct 2004 5:04 PM
Environment: WinXPSP2, JDK/J2SE 1.5/5.0
Description:
When compiling without Maven, everything works fine.
When compiling with Maven, it says that getTextContent and setTextContent (DOM) are
not found.
maven.compile.source=1.5
maven.compile.target=1.5
java:compile:
[echo] Compiling to E:\devel\excp/target/classes
[javac] Compiling 13 source files to E:\devel\excp\target\classes
E:\devel\excp\src\java\org\eoti\tools\excp\cfg\DOMWrapper.java:108: cannot find symbol
symbol : method setTextContent(java.lang.String)
location: interface org.w3c.dom.Element
cp.setTextContent(url.toExternalForm());
^
E:\devel\excp\src\java\org\eoti\tools\excp\cfg\EXCPDomNode.java:57: cannot find symbol
symbol : method getTextContent()
location: interface org.w3c.dom.Node
public String getText(){return node.getTextContent().trim();}
^
2 errors
BUILD FAILED
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1475) Add a faq entry about code sharing
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1475 Here is an overview of the issue: - Key: MAVEN-1475 Summary: Add a faq entry about code sharing Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: documentation Assignee: Reporter: Julien Kirch Created: Thu, 21 Oct 2004 5:48 PM Updated: Thu, 21 Oct 2004 5:48 PM Description: I saw several times the discussion : Q : how to share code between projects A: write a plugin here the faq entry - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1475) Add a faq entry about code sharing
The following issue has been updated: Updater: Julien Kirch (mailto:[EMAIL PROTECTED] ) Date: Thu, 21 Oct 2004 5:49 PM Comment: patch Changes: Attachment changed to faq.patch - For a full history of the issue, see: http://jira.codehaus.org/browse/MAVEN-1475?page=history - View the issue: http://jira.codehaus.org/browse/MAVEN-1475 Here is an overview of the issue: - Key: MAVEN-1475 Summary: Add a faq entry about code sharing Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: documentation Assignee: Reporter: Julien Kirch Created: Thu, 21 Oct 2004 5:48 PM Updated: Thu, 21 Oct 2004 5:49 PM Description: I saw several times the discussion : Q : how to share code between projects A: write a plugin here the faq entry - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: can't create an issue on jira
Arnaud HERITIER wrote: Your permissions seems ok :-( You are in jira-users group and jira-users can create issues on maven ! Arnaud For information the issue was a bad cased login : with the appropriate case all is ok, if you have the same problem think to it. thanks to Mr.Heritier and Walding for their help. Julien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-51) Bad .classpath generated if a test resource matches the source dir (and vice-versa)
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-51
Here is an overview of the issue:
-
Key: MPECLIPSE-51
Summary: Bad .classpath generated if a test resource matches the source dir (and
vice-versa)
Type: Bug
Status: Open
Priority: Major
Original Estimate: 30 minutes
Time Spent: Unknown
Remaining: 30 minutes
Project: maven-eclipse-plugin
Fix Fors:
1.9
Versions:
1.8
Assignee: Felipe Leme
Reporter: Felipe Leme
Created: Fri, 22 Oct 2004 12:22 AM
Updated: Fri, 22 Oct 2004 12:22 AM
Description:
The classpath templates avoid duplicated entries by checking if a resource dir doesn't
conflict with the source dir:
j:if test=${!resourceDirectory.equals(srcDir)}
classpathentry kind=src path=${resourceDirectory}
including=${includingAsString} excluding=${excludingAsString} /
/j:if
But the test above doesn't catch the situation where a test resource uses the source
dir (and vice versa).
I will fix it...
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-52) Test case is failing
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-52 Here is an overview of the issue: - Key: MPECLIPSE-52 Summary: Test case is failing Type: Bug Status: Unassigned Priority: Critical Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Fix Fors: 1.9 Versions: 1.9 Assignee: Reporter: Felipe Leme Created: Fri, 22 Oct 2004 1:06 AM Updated: Fri, 22 Oct 2004 1:06 AM Description: .jelly Element... ant:fail Line.. 395 Column 19 Expected [6] but got [7].Wrong number of generated src directories found Total time: 17 seconds Finished at: Fri Oct 22 02:59:34 BRST 2004 The wrong entry is: classpathentry kind=src path=. /classpathentry (In fact, the .classpath generated by the plugin causes an error when read by eclipse). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-51) Bad .classpath generated if a test resource matches the source dir (and vice-versa)
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-51
Here is an overview of the issue:
-
Key: MPECLIPSE-51
Summary: Bad .classpath generated if a test resource matches the source dir (and
vice-versa)
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: 30 minutes
Time Spent: Unknown
Remaining: 30 minutes
Project: maven-eclipse-plugin
Fix Fors:
1.9
Versions:
1.8
Assignee: Felipe Leme
Reporter: Felipe Leme
Created: Fri, 22 Oct 2004 12:22 AM
Updated: Fri, 22 Oct 2004 1:42 AM
Description:
The classpath templates avoid duplicated entries by checking if a resource dir doesn't
conflict with the source dir:
j:if test=${!resourceDirectory.equals(srcDir)}
classpathentry kind=src path=${resourceDirectory}
including=${includingAsString} excluding=${excludingAsString} /
/j:if
But the test above doesn't catch the situation where a test resource uses the source
dir (and vice versa).
I will fix it...
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/eclipse/src/plugin-test/src/cactus-test - New directory
felipeal2004/10/21 22:55:30 maven-plugins/eclipse/src/plugin-test/src/cactus-test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
