[jira] Created: (MAVENUPLOAD-1879) Synchronize loom repository with central
Synchronize loom repository with central Key: MAVENUPLOAD-1879 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1879 Project: maven-upload-requests Issue Type: Task Reporter: Ignacio Coloma Attachments: org.extrema.loom.sh As indicated in the maven instructions, we have created a repository under http://loom.sourceforge.net/repository We would like to synchronize with central. You can find the script attached. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-81) Suppressing application.xml creation (and inclusion) completely
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118201 ] Stephane Nicoll commented on MEAR-81: - Set the version to 5 and it won't complain anymore. > Suppressing application.xml creation (and inclusion) completely > --- > > Key: MEAR-81 > URL: http://jira.codehaus.org/browse/MEAR-81 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 > Environment: Glassfish V2 appserver >Reporter: Andri Saar >Priority: Minor > > Currently, the maven EAR plugin requires you to include an application.xml > descriptor in every EAR file; however, according to the Java EE 5 spec, this > descriptor is now considered optional. > Furthermore, the existence of application.xml appears to change the semantics > of how the application is deployed, at least on Glassfish V2 (if > application.xml exists, EJB3 beans with just a local > interface are not registered in the JNDI directory; if application.xml is not > there, all beans are registered in JNDI). > I can suppress the automatic creation of application.xml with the > generateApplicationXml parameter; however, if I do that, maven-ear-plugin > starts complaining about not finding application.xml, and currently there is > no way (or at least I didn't find any easy way) to stop maven-ear-plugin from > trying to include the application.xml. > It would be great if maven-ear-plugin provided a parameter, say > suppressApplicationXml, with what you could force maven-ear-plugin not to > include an application.xml in the generated EAR file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-81) Suppressing application.xml creation (and inclusion) completely
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118202 ] Stephane Nicoll commented on MEAR-81: - oops my bad. I thought it was done but it isn't actually. Will do. > Suppressing application.xml creation (and inclusion) completely > --- > > Key: MEAR-81 > URL: http://jira.codehaus.org/browse/MEAR-81 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 > Environment: Glassfish V2 appserver >Reporter: Andri Saar >Priority: Minor > > Currently, the maven EAR plugin requires you to include an application.xml > descriptor in every EAR file; however, according to the Java EE 5 spec, this > descriptor is now considered optional. > Furthermore, the existence of application.xml appears to change the semantics > of how the application is deployed, at least on Glassfish V2 (if > application.xml exists, EJB3 beans with just a local > interface are not registered in the JNDI directory; if application.xml is not > there, all beans are registered in JNDI). > I can suppress the automatic creation of application.xml with the > generateApplicationXml parameter; however, if I do that, maven-ear-plugin > starts complaining about not finding application.xml, and currently there is > no way (or at least I didn't find any easy way) to stop maven-ear-plugin from > trying to include the application.xml. > It would be great if maven-ear-plugin provided a parameter, say > suppressApplicationXml, with what you could force maven-ear-plugin not to > include an application.xml in the generated EAR file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPECLIPSE-70) Make it possible to add linked resources
[
http://jira.codehaus.org/browse/MPECLIPSE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118204
]
ddd commented on MPECLIPSE-70:
--
Felipe that is exactly my case. I have multiple projects in workspace that
should be built into single war and target directory should be same for all
projects so I can point tomcat to it. Currently I do that manualy by adding
following in .project file:
TARGET_DIR
2
TARGET_DIR
TARGET_DIR_TEST
2
TARGET_DIR_TEST
> Make it possible to add linked resources
>
>
> Key: MPECLIPSE-70
> URL: http://jira.codehaus.org/browse/MPECLIPSE-70
> Project: Maven 1.x Eclipse Plugin
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Felipe Leme
>Priority: Minor
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I have some projects that share some common Java files (in a ../common
> directory) and I need to access that directory as a source tree (I know that
> having multiple source directory is not the maven way of doing things, but
> sometimes that's a need).
> So, one way to do this is creating a folder on the project as a link to an
> existing one in the filesystem (or to an Eclipse variable). If I do so on
> Eclipse, it generates an entry like the following in .project:
>
>
> folder_A
> 2
> FOLDER_VARIABLE_NAME
>
>
> file_B
> 1
> /folder/location/on/filesystem
>
>
> So, I think it would be nice to have a property (similar to what we have on
> the natures element) to add such links. Something like this:
> maven.eclipse.links=folderA, fileB
> maven.eclipse.links.folderA.name=folder_A
> maven.eclipse.links.folderA.type=2
> maven.eclipse.links.folderA.location=FOLDER_VARIABLE_NAME
> maven.eclipse.links.fileB.name=file_B
> maven.eclipse.links.fileB.type=1
> maven.eclipse.links.fileB.location=/folder/location/on/filesystem
> Optional, we could eliminate the need for a type variable by using variable
> or path:
> maven.eclipse.links.folderA.name=folder_A
> maven.eclipse.links.folderA.variable=FOLDER_VARIABLE_NAME
> maven.eclipse.links.fileB.name=file_B
> maven.eclipse.links.fileB.path=/folder/location/on/filesystem
>
>
>
> ${maven.eclipse.links}
>
>
>
>
>
>
> ${context.getVariable(name)}
> ${context.getVariable(link)}
> ${context.getVariable(location)}
>
>
>
> -- Felipe
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-258) Sync usage guide with Maven standard directory layout
Sync usage guide with Maven standard directory layout - Key: MASSEMBLY-258 URL: http://jira.codehaus.org/browse/MASSEMBLY-258 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Reporter: Benjamin Bentmann Priority: Trivial Attachments: directory-layout.patch According to [http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html] and [http://docs.codehaus.org/display/MAVENUSER/The+Standard+Directory+Layout], assembly descriptors should be stored under "src/main/assembly". The usage guide currenlty suggests to use "src/assembly" which misleads the reader to break with the standard directory layout. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-255) type in error message
[ http://jira.codehaus.org/browse/MASSEMBLY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MASSEMBLY-255: Attachment: windows-eol.patch I think given the fact that DOS is rather historical, "windows" should be a valid synonym for CRLF line endings as provided by the patch. > type in error message > - > > Key: MASSEMBLY-255 > URL: http://jira.codehaus.org/browse/MASSEMBLY-255 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Cygwin, XP, Java 1.5 >Reporter: blue >Priority: Trivial > Attachments: windows-eol.patch > > > Accidentally used "windows" instead of "dos" as a line ending type, and it > spit this message: > [ERROR] BUILD ERROR > [INFO] > [INFO] Failed to create assembly: Illlegal lineEnding specified: 'windows' > (Illegal has one too many L's) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAR-13) configure test-jar to include only special classes of the test source
[ http://jira.codehaus.org/browse/MJAR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible closed MJAR-13. -- Resolution: Duplicate Duplicated by XSTR-30 > configure test-jar to include only special classes of the test source > - > > Key: MJAR-13 > URL: http://jira.codehaus.org/browse/MJAR-13 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Joerg Schaible >Priority: Minor > > The test-jar currently contains all test classes, but often you just want to > share only some parts of it, e.g. a specialized abstract TestCase or a test > toolkit or some mock classes, but not the complete unit test for an > asrtifact. The plugin configuration shoulds contain a section with an > includes/excludes pattern set. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-13) configure test-jar to include only special classes of the test source
[ http://jira.codehaus.org/browse/MJAR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118220 ] Dennis Lundberg commented on MJAR-13: - Did you really mean XSTR-30 ? > configure test-jar to include only special classes of the test source > - > > Key: MJAR-13 > URL: http://jira.codehaus.org/browse/MJAR-13 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Joerg Schaible >Priority: Minor > > The test-jar currently contains all test classes, but often you just want to > share only some parts of it, e.g. a specialized abstract TestCase or a test > toolkit or some mock classes, but not the complete unit test for an > asrtifact. The plugin configuration shoulds contain a section with an > includes/excludes pattern set. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-82) Class-Path manifest entry should support maven repository layout
[
http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118221
]
Dennis Lundberg commented on MJAR-82:
-
I've changed the name of the parameter so it is now called
{code:xml}
true
{code}
This was made so that the capitalization of the word classpath is consistent
between the different parameters.
> Class-Path manifest entry should support maven repository layout
>
>
> Key: MJAR-82
> URL: http://jira.codehaus.org/browse/MJAR-82
> Project: Maven 2.x Jar Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Geoffrey De Smet
>Assignee: Olivier Lamy
> Fix For: 2.2
>
>
> The assembly plugin supports outputting all dependencies in a repository
> layout.
> The jar plugin should support adding the classpath manifest entry based on
> the repository layout.
> The combination of the two makes it easy to write a script to run the app:
> "java -jar org/domain/project/projectApp.jar" at the base of the repository
> layout.
> Example of a Class-Path entry:
> ClassPath:
> org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar
> Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in
> "
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-13) configure test-jar to include only special classes of the test source
[ http://jira.codehaus.org/browse/MJAR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118224 ] Joerg Schaible commented on MJAR-13: Sorry, no, MJAR-30 :-) > configure test-jar to include only special classes of the test source > - > > Key: MJAR-13 > URL: http://jira.codehaus.org/browse/MJAR-13 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Joerg Schaible >Priority: Minor > > The test-jar currently contains all test classes, but often you just want to > share only some parts of it, e.g. a specialized abstract TestCase or a test > toolkit or some mock classes, but not the complete unit test for an > asrtifact. The plugin configuration shoulds contain a section with an > includes/excludes pattern set. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCOMPILER-59) Compilation fails on warning messages from javac (Java 6)
[ http://jira.codehaus.org/browse/MCOMPILER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Bach updated MCOMPILER-59: Attachment: warning.tar.gz > Compilation fails on warning messages from javac (Java 6) > - > > Key: MCOMPILER-59 > URL: http://jira.codehaus.org/browse/MCOMPILER-59 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Mac OSX 10.4.10 > Maven version: 2.0.7 > Java version: 1.6.0-dp > OS name: "mac os x" version: "10.4.10" arch: "i386" > java version "1.6.0-dp" > Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) > Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing) >Reporter: Tim Meighen > Attachments: compiler-warning.tar.gz, warning.tar.gz > > > The attached project fails due to an inability to parse the following warning > messages from the Java compiler (Java 6) > [INFO] Compilation failure > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-59) Compilation fails on warning messages from javac (Java 6)
[ http://jira.codehaus.org/browse/MCOMPILER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118230 ] Christian Bach commented on MCOMPILER-59: - The project in the second attachment fails in similar fashion when built using Java 6 on Linux. The problem is rooted in the plexus-compiler plugin which, in its current version 1.5.3, is not capable of parsing Java 6 warning and/or error messages properly. > Compilation fails on warning messages from javac (Java 6) > - > > Key: MCOMPILER-59 > URL: http://jira.codehaus.org/browse/MCOMPILER-59 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Mac OSX 10.4.10 > Maven version: 2.0.7 > Java version: 1.6.0-dp > OS name: "mac os x" version: "10.4.10" arch: "i386" > java version "1.6.0-dp" > Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) > Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing) >Reporter: Tim Meighen > Attachments: compiler-warning.tar.gz, warning.tar.gz > > > The attached project fails due to an inability to parse the following warning > messages from the Java compiler (Java 6) > [INFO] Compilation failure > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCOMPILER-59) Compilation fails on warning messages from javac (Java 6)
[ http://jira.codehaus.org/browse/MCOMPILER-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118230 ] thabach edited comment on MCOMPILER-59 at 12/30/07 1:34 PM: --- The project in the second attachment fails in similar fashion when built using Java 6 on Linux. The problem is rooted in the compiler-plugin's dependency on plexus-compiler-javac which, in its current version 1.5.3, is not capable of parsing Java 6 warning and/or error messages properly. was (Author: thabach): The project in the second attachment fails in similar fashion when built using Java 6 on Linux. The problem is rooted in the plexus-compiler plugin which, in its current version 1.5.3, is not capable of parsing Java 6 warning and/or error messages properly. > Compilation fails on warning messages from javac (Java 6) > - > > Key: MCOMPILER-59 > URL: http://jira.codehaus.org/browse/MCOMPILER-59 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Mac OSX 10.4.10 > Maven version: 2.0.7 > Java version: 1.6.0-dp > OS name: "mac os x" version: "10.4.10" arch: "i386" > java version "1.6.0-dp" > Java(TM) SE Runtime Environment (build 1.6.0-dp-b88-34) > Java HotSpot(TM) Client VM (build 1.6.0-b88-17-release, mixed mode, sharing) >Reporter: Tim Meighen > Attachments: compiler-warning.tar.gz, warning.tar.gz > > > The attached project fails due to an inability to parse the following warning > messages from the Java compiler (Java 6) > [INFO] Compilation failure > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ > could not parse error message: > /Users/tmeighen/compiler-warning/entity/target/classes/test/MyEntity.class: > warning: Cannot find annotation method 'name()' in type > 'javax.persistence.Table': class file for javax.persistence.Table not found > /Users/tmeighen/compiler-warning/logic/src/main/java/test/Logic.java:7: > warning: [deprecation] deprecateMe() in test.MyEntity has been deprecated > entity.deprecateMe(); > ^ -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3342) Impossible to create entries with empty value in MANIFEST
Impossible to create entries with empty value in MANIFEST - Key: MNG-3342 URL: http://jira.codehaus.org/browse/MNG-3342 Project: Maven 2 Issue Type: Bug Components: maven-archiver Affects Versions: Reviewed Pending Version Assignment Reporter: Olivier Lamy Regression due to patch for MJAR-38 (svn rev 415208 in maven-archiver ). It's now impossible to create entries with empty value in MANIFEST file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3342) Impossible to create entries with empty value in MANIFEST
[ http://jira.codehaus.org/browse/MNG-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-3342: -- Assignee: Olivier Lamy > Impossible to create entries with empty value in MANIFEST > - > > Key: MNG-3342 > URL: http://jira.codehaus.org/browse/MNG-3342 > Project: Maven 2 > Issue Type: Bug > Components: maven-archiver >Affects Versions: Reviewed Pending Version Assignment >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > Regression due to patch for MJAR-38 (svn rev 415208 in maven-archiver ). > It's now impossible to create entries with empty value in MANIFEST file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MJAR-59) Impossible to create empty entries in MANIFEST
[ http://jira.codehaus.org/browse/MJAR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118093 ] olamy edited comment on MJAR-59 at 12/30/07 3:34 PM: Regression due to patch for MJAR-38. svn rev 415208 in maven-archiver (http://fisheye6.cenqua.com/browse/maven/shared/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java?r=415208#l96). As we have to preserve backward comp, we must restore the capability to have manifest entries with empty value. (MNG-3342) was (Author: olamy): Regression due to patch for MJAR-38. svn rev 415208 in maven-archiver (http://fisheye6.cenqua.com/browse/maven/shared/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java?r=415208#l96). As we have to preserve backward comp, IMHO we can add a new configuration parameter in maven-archiver : isAcceptEmptyManifestEntries (default value false). This issue can be move to maven-archiver (or clone and link to this one). Thoughts ? > Impossible to create empty entries in MANIFEST > -- > > Key: MJAR-59 > URL: http://jira.codehaus.org/browse/MJAR-59 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stéphane Veyret >Priority: Minor > > With the new version of archiver, that allow us to remove pre-defined default > entries in MANIFEST, if we specify an empty entry (i.e. > MyEntry: > ), instead of adding the entry, the archiver removes an eventually existing > one with that name. This means the JAR plugin does not work as before. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3342) Impossible to create entries with empty value in MANIFEST
[ http://jira.codehaus.org/browse/MNG-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-3342. - Resolution: Fixed committed in rev 607603. > Impossible to create entries with empty value in MANIFEST > - > > Key: MNG-3342 > URL: http://jira.codehaus.org/browse/MNG-3342 > Project: Maven 2 > Issue Type: Bug > Components: maven-archiver >Affects Versions: Reviewed Pending Version Assignment >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > Regression due to patch for MJAR-38 (svn rev 415208 in maven-archiver ). > It's now impossible to create entries with empty value in MANIFEST file. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAR-59) Impossible to create empty entries in MANIFEST
[ http://jira.codehaus.org/browse/MJAR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MJAR-59. Assignee: Olivier Lamy Resolution: Fixed Fix Version/s: 2.2 fix in maven-archiver. > Impossible to create empty entries in MANIFEST > -- > > Key: MJAR-59 > URL: http://jira.codehaus.org/browse/MJAR-59 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stéphane Veyret >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.2 > > > With the new version of archiver, that allow us to remove pre-defined default > entries in MANIFEST, if we specify an empty entry (i.e. > MyEntry: > ), instead of adding the entry, the archiver removes an eventually existing > one with that name. This means the JAR plugin does not work as before. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-58) Update Jar Plugin Documentation (more examples for manifest customization)
[ http://jira.codehaus.org/browse/MJAR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118248 ] Olivier Lamy commented on MJAR-58: -- MNG-3329 improve archiver configuration documentation. We just have to add a link to this somewhere in jar plugin site. > Update Jar Plugin Documentation (more examples for manifest customization) > -- > > Key: MJAR-58 > URL: http://jira.codehaus.org/browse/MJAR-58 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Franz Allan Valencia See >Priority: Minor > Fix For: 2.2 > > > The current jarplugin documentations has an example on how to customize the > manifest to be generated. Furthermore, it provides a link to the javadoc of > MavenArchiveConfiguration, which implies under configurations aside from the > one shown there (manifest entries). > IMHO, we can remove the link to the javadoc and replace that with actual > examples of those configurations. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-127) Take advantage of PLXCOMP-76
Take advantage of PLXCOMP-76 Key: MDEP-127 URL: http://jira.codehaus.org/browse/MDEP-127 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: unpack, unpack-dependencies Affects Versions: 2.0-alpha-4 Environment: xp,linux,solaris Reporter: Dan Tran Assignee: Brian Fox need to release plexus-archiver first -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
