[jira] Closed: (MEV-322) hibernate-tools 3.1.0.beta4 has invalid jtidy dependency
[ http://jira.codehaus.org/browse/MEV-322?page=all ] Tomislav Stojcevich closed MEV-322: --- Resolution: Fixed This was fixed when jtidy was re-uploaded to the correct location. Ignore this request. > hibernate-tools 3.1.0.beta4 has invalid jtidy dependency > > > Key: MEV-322 > URL: http://jira.codehaus.org/browse/MEV-322 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Attachments: hibernate-tools-3.1.0.beta4.pom > > > It looks like this special version of jtidy was deployed with the r8 as part > of the name rather than the version. > The dependency in the hibernate-tools-3.1.0.beta4 needs to be updated to: > > org.hibernate > jtidy-r8 > 21122004 > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-719) CLONE -Upload AjaxTags library - sources
[ http://jira.codehaus.org/browse/MAVENUPLOAD-719?page=comments#action_57742 ] Tomislav Stojcevich commented on MAVENUPLOAD-719: - Cloning this because I can't reopen MAVENUPLOAD-659 since I am not the Reporter. The library did get uploaded but the sources did not and they were part of the upload bundle in MAVENUPLOAD-659 Please add the sources. Thanks. > CLONE -Upload AjaxTags library - sources > > > Key: MAVENUPLOAD-719 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-719 > Project: maven-upload-requests > Type: Task > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-712: - The sources were not uploaded and they are in the upload bundle. Please upload the sources. Thanks. > Upload hibernate-tools-3.1.0.beta4 > -- > > Key: MAVENUPLOAD-712 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, > hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar, > jtidy-r8-21122004-bundle.jar > > > Upload new version. > Also attached is special version of jtidy that is distributed with the > package, the groupid is set to org.hibernate.hibernate-tools for this version > as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-719) CLONE -Upload AjaxTags library - sources
CLONE -Upload AjaxTags library - sources Key: MAVENUPLOAD-719 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-719 Project: maven-upload-requests Type: Task Reporter: Tomislav Stojcevich Assigned to: Carlos Sanchez Hi, Please upload the AjaxTags library version 1.1.5. The project url is located http://ajaxtags.sourceforge.net. Download link : http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 This project is build with maven1. Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-322) hibernate-tools 3.1.0.beta4 has invalid jtidy dependency
[ http://jira.codehaus.org/browse/MEV-322?page=all ] Tomislav Stojcevich updated MEV-322: Attachment: hibernate-tools-3.1.0.beta4.pom > hibernate-tools 3.1.0.beta4 has invalid jtidy dependency > > > Key: MEV-322 > URL: http://jira.codehaus.org/browse/MEV-322 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Attachments: hibernate-tools-3.1.0.beta4.pom > > > It looks like this special version of jtidy was deployed with the r8 as part > of the name rather than the version. > The dependency in the hibernate-tools-3.1.0.beta4 needs to be updated to: > > org.hibernate > jtidy-r8 > 21122004 > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-322) hibernate-tools 3.1.0.beta4 has invalid jtidy dependency
hibernate-tools 3.1.0.beta4 has invalid jtidy dependency Key: MEV-322 URL: http://jira.codehaus.org/browse/MEV-322 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Tomislav Stojcevich It looks like this special version of jtidy was deployed with the r8 as part of the name rather than the version. The dependency in the hibernate-tools-3.1.0.beta4 needs to be updated to: org.hibernate jtidy-r8 21122004 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=comments#action_57624 ] Tomislav Stojcevich commented on MAVENUPLOAD-659: - The sources did not make it into the repository. > Upload AjaxTags library > --- > > Key: MAVENUPLOAD-659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 > Project: maven-upload-requests > Type: Task > Reporter: Olivier Lamy > Assignee: Carlos Sanchez > Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5-bundle.jar, > ajaxtags-1.1.5.jar, project.xml > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-714) Upload jericho-html-1.5-dev1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-714?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-714: - The sources did not make it into the repository. > Upload jericho-html-1.5-dev1.jar > > > Key: MAVENUPLOAD-714 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-714 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: jericho-html-1.5-dev1-bundle.jar > > > Upload jar. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1544) Attached artefacts not handled
[ http://jira.codehaus.org/browse/MNG-1544?page=all ]
Tomislav Stojcevich updated MNG-1544:
-
Attachment: MNG-1544-maven-artifact-ant.patch
MNG-1544-site.patch
> Attached artefacts not handled
> --
>
> Key: MNG-1544
> URL: http://jira.codehaus.org/browse/MNG-1544
> Project: Maven 2
> Type: Bug
> Components: Ant tasks
> Versions: 2.0
> Reporter: Tomislav Bodor
> Fix For: 2.1
> Attachments: MNG-1544-maven-artifact-ant.patch, MNG-1544-site.patch
>
>
> The install and deploy tasks don't seem to be able to handle attached
> artefacts. There appear to be two sides to the problem: first, there seems to
> be no way to attach anything, and second, even if it were attached, the
> install and deploy tasks don't do anything with attachments.
> The latter could be solved by adding to the install (and similar to the
> deploy) task something along the lines of (similar to the InstallMojo in the
> install plugin):
> List attachedArtifacts =
> pom.getMavenProject().getAttachedArtifacts();
> for (Iterator i = attachedArtifacts.iterator(); i.hasNext(); ) {
> Artifact attached = (Artifact) i.next();
> installer.install(attached.getFile(), attached, localRepo);
> }
> For the former (how to attach anything), a new task could be added (say,
> 'attach', taking a type, classifier and file).
> This functionality is needed to handle source archives and EJB client jars.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-709) Upload extremecomponents 1.0.1-M4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-709?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-709: - The sources didn't seem to make it into the repository. > Upload extremecomponents 1.0.1-M4 > - > > Key: MAVENUPLOAD-709 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-709 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: extremecomponents-1.0.1-M4-bundle.jar > > > Upload new version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=comments#action_57480 ] Tomislav Stojcevich commented on MAVENUPLOAD-712: - Ignore the jtidy, it was taken care of in MAVENUPLOAD-690 > Upload hibernate-tools-3.1.0.beta4 > -- > > Key: MAVENUPLOAD-712 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, > hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar, > jtidy-r8-21122004-bundle.jar > > > Upload new version. > Also attached is special version of jtidy that is distributed with the > package, the groupid is set to org.hibernate.hibernate-tools for this version > as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2
[ http://jira.codehaus.org/browse/MNG-1980?page=comments#action_57467 ] Tomislav Stojcevich commented on MNG-1980: -- I didn't have maven-project updated. I assumed the change was in maven-artifact-ant. You are correct, the message only appears in the 2.0.3 version. After rebuilding and testing, 2.0.3-SNAPSHOT still produces this error, 2.1-SNAPSHOT seems to have corrected it. Will it be fixed for 2.0.3 or must we wait until 2.1? The "Fix Version/s" is currently set at 2.0.3 for this issue. > "Duplicate project ID found" message with maven-artifact-ant-2.0.2 > -- > > Key: MNG-1980 > URL: http://jira.codehaus.org/browse/MNG-1980 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0.2 > Reporter: Tomislav Stojcevich > Assignee: Jason van Zyl > Fix For: 2.0.3 > > > The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2. > [artifact:install] An error has occurred while processing the Maven artifact > tasks. > [artifact:install] Diagnosis: > [artifact:install] > [artifact:install] Unable to build project: > D:\Projects\Development\app\pom.xml > [artifact:install] Duplicate project ID found in > D:\Projects\Development\app\pom.xml > [artifact:install] > BUILD FAILED > D:\Projects\Development\app\ant\build.xml:166: Unable to build project: > D:\Projects\Development\app\pom.xml -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2
[ http://jira.codehaus.org/browse/MNG-1980?page=all ] Tomislav Stojcevich reopened MNG-1980: -- Why was this closed? The problem still exists. I checkout and rebuild from both the trunk and 2.0.3 branches and I still get the same error with both versions. > "Duplicate project ID found" message with maven-artifact-ant-2.0.2 > -- > > Key: MNG-1980 > URL: http://jira.codehaus.org/browse/MNG-1980 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0.2 > Reporter: Tomislav Stojcevich > Assignee: Jason van Zyl > Fix For: 2.0.3 > > > The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2. > [artifact:install] An error has occurred while processing the Maven artifact > tasks. > [artifact:install] Diagnosis: > [artifact:install] > [artifact:install] Unable to build project: > D:\Projects\Development\app\pom.xml > [artifact:install] Duplicate project ID found in > D:\Projects\Development\app\pom.xml > [artifact:install] > BUILD FAILED > D:\Projects\Development\app\ant\build.xml:166: Unable to build project: > D:\Projects\Development\app\pom.xml -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=all ] Tomislav Stojcevich updated MAVENUPLOAD-659: Attachment: ajaxtags-1.1.5-bundle.jar > Upload AjaxTags library > --- > > Key: MAVENUPLOAD-659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 > Project: maven-upload-requests > Type: Task > Reporter: Olivier Lamy > Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5-bundle.jar, > ajaxtags-1.1.5.jar, project.xml > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-714) Upload jericho-html-1.5-dev1.jar
Upload jericho-html-1.5-dev1.jar Key: MAVENUPLOAD-714 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-714 Project: maven-upload-requests Type: Bug Reporter: Tomislav Stojcevich Attachments: jericho-html-1.5-dev1-bundle.jar Upload jar. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=comments#action_57373 ] Tomislav Stojcevich commented on MAVENUPLOAD-659: - jericho-html is available in html/parser but it is the 2.1 version. This version of ajaxtags ships with the 1.5-dev1 version. I don't feel comfortable changing the pom to point to the 2.1 version since it may not be compatable. Is it possible to get the 1.5dev1 version uploaded into the central repo? If I'm correct, dev versions are not allowed. > Upload AjaxTags library > --- > > Key: MAVENUPLOAD-659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 > Project: maven-upload-requests > Type: Task > Reporter: Olivier Lamy > Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5.jar, project.xml > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=all ] Tomislav Stojcevich updated MAVENUPLOAD-712: Attachment: jtidy-r8-21122004-bundle.jar hibernate-tools-3.1.0.beta4-bundle.jar > Upload hibernate-tools-3.1.0.beta4 > -- > > Key: MAVENUPLOAD-712 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, > hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar, > jtidy-r8-21122004-bundle.jar > > > Upload new version. > Also attached is special version of jtidy that is distributed with the > package, the groupid is set to org.hibernate.hibernate-tools for this version > as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4
Upload hibernate-tools-3.1.0.beta4 -- Key: MAVENUPLOAD-712 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712 Project: maven-upload-requests Type: Bug Reporter: Tomislav Stojcevich Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar Upload new version. Also attached is special version of jtidy that is distributed with the package, the groupid is set to org.hibernate.hibernate-tools for this version as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-709) Upload extremecomponents 1.0.1-M4
Upload extremecomponents 1.0.1-M4 - Key: MAVENUPLOAD-709 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-709 Project: maven-upload-requests Type: Bug Reporter: Tomislav Stojcevich Attachments: extremecomponents-1.0.1-M4-bundle.jar Upload new version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-689) Add javax.ejb 2.1 pom to maven2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-689?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-689: - I don't see it out in the repository yet. It's been a couple of days now. > Add javax.ejb 2.1 pom to maven2 repo > > > Key: MAVENUPLOAD-689 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-689 > Project: maven-upload-requests > Type: Bug > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: ejb-2.1.pom > > > This jar is a sun proprietary jar so here is just the pom copied from the 2.0 > version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-689) Add javax.ejb 2.1 pom to maven2 repo
Add javax.ejb 2.1 pom to maven2 repo Key: MAVENUPLOAD-689 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-689 Project: maven-upload-requests Type: Bug Reporter: Tomislav Stojcevich Attachments: ejb-2.1.pom This jar is a sun proprietary jar so here is just the pom copied from the 2.0 version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2
"Duplicate project ID found" message with maven-artifact-ant-2.0.2 -- Key: MNG-1980 URL: http://jira.codehaus.org/browse/MNG-1980 Project: Maven 2 Type: Bug Components: Ant tasks Versions: 2.0.2 Reporter: Tomislav Stojcevich The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2. [artifact:install] An error has occurred while processing the Maven artifact tasks. [artifact:install] Diagnosis: [artifact:install] [artifact:install] Unable to build project: D:\Projects\Development\app\pom.xml [artifact:install] Duplicate project ID found in D:\Projects\Development\app\pom.xml [artifact:install] BUILD FAILED D:\Projects\Development\app\ant\build.xml:166: Unable to build project: D:\Projects\Development\app\pom.xml -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1970) maven-artifact-ant-2.0.2-dep.jar missing antlib.xml
[ http://jira.codehaus.org/browse/MNG-1970?page=comments#action_56209 ] Tomislav Stojcevich commented on MNG-1970: -- I re-downloaded the jar today to see if maybe it was a syncing issue or something and the jar I got was labeled as a 2.0.2 jar and it did have in it antlib.xml and the class files but it has the Duplicate project ID bug in it. > maven-artifact-ant-2.0.2-dep.jar missing antlib.xml > --- > > Key: MNG-1970 > URL: http://jira.codehaus.org/browse/MNG-1970 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0.2 > Reporter: Tomislav Stojcevich > > > It looks like the antlib.xml file is missing from the released jar. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1970) maven-artifact-ant-2.0.2-dep.jar missing antlib.xml
[ http://jira.codehaus.org/browse/MNG-1970?page=comments#action_56091 ] Tomislav Stojcevich commented on MNG-1970: -- None of the class files for the ant tasks are there either. The entire org/apache/maven/artifact/ant package is missing. > maven-artifact-ant-2.0.2-dep.jar missing antlib.xml > --- > > Key: MNG-1970 > URL: http://jira.codehaus.org/browse/MNG-1970 > Project: Maven 2 > Type: Bug > Components: Ant tasks > Versions: 2.0.2 > Reporter: Tomislav Stojcevich > > > It looks like the antlib.xml file is missing from the released jar. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1970) maven-artifact-ant-2.0.2-dep.jar missing antlib.xml
maven-artifact-ant-2.0.2-dep.jar missing antlib.xml --- Key: MNG-1970 URL: http://jira.codehaus.org/browse/MNG-1970 Project: Maven 2 Type: Bug Components: Ant tasks Versions: 2.0.2 Reporter: Tomislav Stojcevich It looks like the antlib.xml file is missing from the released jar. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-659) Upload AjaxTags library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=all ] Tomislav Stojcevich updated MAVENUPLOAD-659: Attachment: ajaxtags-1.1.5-bundle.jar > Upload AjaxTags library > --- > > Key: MAVENUPLOAD-659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659 > Project: maven-upload-requests > Type: Task > Reporter: Olivier Lamy > Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5.jar, project.xml > > > Hi, > Please upload the AjaxTags library version 1.1.5. > The project url is located http://ajaxtags.sourceforge.net. > Download link : > http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728 > This project is build with maven1. > Thanks, -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-661) add sources to commons-net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-661?page=all ] Tomislav Stojcevich updated MAVENUPLOAD-661: Attachment: sources.zip > add sources to commons-net > -- > > Key: MAVENUPLOAD-661 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-661 > Project: maven-upload-requests > Type: Improvement > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: commons-net-1.4.1-sources.jar, sources.zip > > > Not sure if this is the correct place to request this but can you please add > this sources.jar to the repository. > Not creating a bundle because it is an apache project that is sync'd from the > apache repository. > I only the sources need to be added. > Let me know if there is another mechanism to handle this. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-661) add sources to commons-net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-661?page=all ] Tomislav Stojcevich reopened MAVENUPLOAD-661: - Are you sure I would need to create a new bundle with the sources? This is an apache project, similar to commons-beanutils and commons-collections. Both of those have sources and I can't find an upload request for either of them with bundles. They get their main jar sync'd from the apache repository. Is there a similar location for automatic syncing of their sources? I can create a new bundle but there is risk of me somehow accidentially submitting with the wrong pom or something. I have more than just this one, probabably about 10 or so more that I would like source for, almost all are apache projects. > add sources to commons-net > -- > > Key: MAVENUPLOAD-661 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-661 > Project: maven-upload-requests > Type: Improvement > Reporter: Tomislav Stojcevich > Assignee: Carlos Sanchez > Attachments: commons-net-1.4.1-sources.jar > > > Not sure if this is the correct place to request this but can you please add > this sources.jar to the repository. > Not creating a bundle because it is an apache project that is sync'd from the > apache repository. > I only the sources need to be added. > Let me know if there is another mechanism to handle this. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-661) add sources to commons-net
add sources to commons-net -- Key: MAVENUPLOAD-661 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-661 Project: maven-upload-requests Type: Improvement Reporter: Tomislav Stojcevich Attachments: commons-net-1.4.1-sources.jar Not sure if this is the correct place to request this but can you please add this sources.jar to the repository. Not creating a bundle because it is an apache project that is sync'd from the apache repository. I only the sources need to be added. Let me know if there is another mechanism to handle this. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-259) commons-net 1.4.1 invalid pom
[ http://jira.codehaus.org/browse/MEV-259?page=all ] Tomislav Stojcevich updated MEV-259: Attachment: commons-net-1.4.1.pom > commons-net 1.4.1 invalid pom > - > > Key: MEV-259 > URL: http://jira.codehaus.org/browse/MEV-259 > Project: Maven Evangelism > Type: Bug > Reporter: Tomislav Stojcevich > Attachments: commons-net-1.4.1.pom > > > The pom is the old maven 1 pom. > 1.4.1 was a minor release. I diffed the maven 1 poms (1.4.0 to 1.4.1) and it > looks like a version number change is all that is required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-259) commons-net 1.4.1 invalid pom
commons-net 1.4.1 invalid pom - Key: MEV-259 URL: http://jira.codehaus.org/browse/MEV-259 Project: Maven Evangelism Type: Bug Reporter: Tomislav Stojcevich The pom is the old maven 1 pom. 1.4.1 was a minor release. I diffed the maven 1 poms (1.4.0 to 1.4.1) and it looks like a version number change is all that is required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-245) Tomcat 4.1.31 missing
[ http://jira.codehaus.org/browse/MEV-245?page=comments#action_52875 ] Tomislav Stojcevich commented on MEV-245: - Shouldn't the sync take care of it? It looks like the jars made it into the maven1 repository. http://www.ibiblio.org/maven/tomcat/jars/ The bottom of the page you referenced states that there is automatic syncronization between apache and ibiblio. > Tomcat 4.1.31 missing > - > > Key: MEV-245 > URL: http://jira.codehaus.org/browse/MEV-245 > Project: Maven Evangelism > Type: Bug > Reporter: Tomislav Stojcevich > > > Not sure if this is the correct place to ask this becase the instructions on > the maven2 site are not specific. Let me know what the correct procedures > are if this is not the right place. > I asked the Tomcat team to add Tomcat 4.1.31 to the Apache repository. They > did that. See: http://www.apache.org/dist/java-repository/tomcat/jars/ > It looks like the directories got created for maven2 but no jars or poms. > What needs to be done now to get the jars and poms in the central repository > for maven2? > Specifically I need jasper-compiler and jasper-runtime. I know somebody else > asked about catalina in the mailing list a while back. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-245) Tomcat 4.1.31 missing
Tomcat 4.1.31 missing - Key: MEV-245 URL: http://jira.codehaus.org/browse/MEV-245 Project: Maven Evangelism Type: Bug Reporter: Tomislav Stojcevich Not sure if this is the correct place to ask this becase the instructions on the maven2 site are not specific. Let me know what the correct procedures are if this is not the right place. I asked the Tomcat team to add Tomcat 4.1.31 to the Apache repository. They did that. See: http://www.apache.org/dist/java-repository/tomcat/jars/ It looks like the directories got created for maven2 but no jars or poms. What needs to be done now to get the jars and poms in the central repository for maven2? Specifically I need jasper-compiler and jasper-runtime. I know somebody else asked about catalina in the mailing list a while back. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-487) Allow for specifying the location of the Ant build file
Allow for specifying the location of the Ant build file --- Key: CONTINUUM-487 URL: http://jira.codehaus.org/browse/CONTINUUM-487 Project: Continuum Type: Improvement Versions: 1.0.1 Reporter: Tomislav Stojcevich Priority: Minor There is currently no way to specify the location of the Ant build file if it does not reside in the project root directory. In some of my projects, the build.xml file is in a subdirectory of the project root directory. -- 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: (CONTINUUM-459) ANT projects ask for POM and Goals when adding build definition
ANT projects ask for POM and Goals when adding build definition --- Key: CONTINUUM-459 URL: http://jira.codehaus.org/browse/CONTINUUM-459 Project: Continuum Type: Bug Versions: 1.0.1 Reporter: Tomislav Stojcevich After adding and ANT project it asks for POM and Goals when adding a build definition. This makes it impossible to setup an ant build file to run (at least I can't figure out another way to make an ANT project run). -- 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: (MEV-195) securityfilter missing dependencies
securityfilter missing dependencies --- Key: MEV-195 URL: http://jira.codehaus.org/browse/MEV-195 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Tomislav Stojcevich Attachments: securityfilter-2.0.pom.patch -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-195) securityfilter missing dependencies
[ http://jira.codehaus.org/browse/MEV-195?page=all ] Tomislav Stojcevich updated MEV-195: Attachment: securityfilter-2.0.pom.patch Attached is the patch file. > securityfilter missing dependencies > --- > > Key: MEV-195 > URL: http://jira.codehaus.org/browse/MEV-195 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Attachments: securityfilter-2.0.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-194) cactus missing dependencies
[ http://jira.codehaus.org/browse/MEV-194?page=all ] Tomislav Stojcevich updated MEV-194: Attachment: cactus-13-1.7.1.pom.patch Here' the patch file with the dependencies. > cactus missing dependencies > --- > > Key: MEV-194 > URL: http://jira.codehaus.org/browse/MEV-194 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Attachments: cactus-13-1.7.1.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-194) cactus missing dependencies
cactus missing dependencies --- Key: MEV-194 URL: http://jira.codehaus.org/browse/MEV-194 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Tomislav Stojcevich -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-192) AXIS 1.3 is missing dependencies
[ http://jira.codehaus.org/browse/MEV-192?page=comments#action_50676 ] Tomislav Stojcevich commented on MEV-192: - Thanks! > AXIS 1.3 is missing dependencies > > > Key: MEV-192 > URL: http://jira.codehaus.org/browse/MEV-192 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: axis-1.3.pom.patch, axis-1.3.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEV-192) AXIS 1.3 is missing dependencies
[ http://jira.codehaus.org/browse/MEV-192?page=all ] Tomislav Stojcevich reopened MEV-192: - It's been over 48 hours and the change still hasn't made it to the central repository. This happened a couple of days ago also. The change for commons-logging-1.1-dev in xdoclet that was also made for another issue is also not yet showing up in the repository. I saw the changes are made in SVN and the timestamps of the files have been updated in the central repository but the file contents haven't changed. Is the sync process broken? > AXIS 1.3 is missing dependencies > > > Key: MEV-192 > URL: http://jira.codehaus.org/browse/MEV-192 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: axis-1.3.pom.patch, axis-1.3.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1403) Add on option to include optional dependencies instead of (or in addition to) excluding optional dependencies
[ http://jira.codehaus.org/browse/MNG-1403?page=comments#action_50599 ] Tomislav Stojcevich commented on MNG-1403: -- I don't see how this is a duplicate of MNG-702. >From the comments it looks like that request resulted in the creation of the >optional tag. What I am requesting is that if the dependency is marked as optional, don't download it by default or create a flag to specify if optionals should or shouldn't be downloaded. Much less of a headache for those of us who only use very few of the dependencies that are marked as optional. > Add on option to include optional dependencies instead of (or in addition to) > excluding optional dependencies > - > > Key: MNG-1403 > URL: http://jira.codehaus.org/browse/MNG-1403 > Project: Maven 2 > Type: Improvement > Versions: 2.0 > Reporter: Tomislav Stojcevich > Assignee: Brett Porter > Priority: Minor > > > It seems backwards to have to exclude optional dependencies. If I have to > declare a dependency, then I am more likely to know which of it's optional > dependencies that I need to include, rather than knowing which to exclude. > This would greatly reduce (and even eliminate) the number of excludes that > are required in my poms. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-145) struts-menu invalid dependencies for m2
[ http://jira.codehaus.org/browse/MEV-145?page=all ] Tomislav Stojcevich updated MEV-145: Attachment: struts-menu-2.3.pom.patch I talked to Matt Raible about marking some of the entries as optional. This patch file contains all changes necessary to make this pom valid. Please apply. Thanks! > struts-menu invalid dependencies for m2 > --- > > Key: MEV-145 > URL: http://jira.codehaus.org/browse/MEV-145 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: struts-menu-2.3.pom, struts-menu-2.3.pom, > struts-menu-2.3.pom.patch > > > In the junit dependency change to > In velocity-tools dep needs to have view- removed from the version and added > to the end of the artifact-id: velocity-tools-view > servletapi shuld have a scope of provided so it is not packaged in the war -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-192) AXIS 1.3 is missing dependencies
[ http://jira.codehaus.org/browse/MEV-192?page=all ] Tomislav Stojcevich updated MEV-192: Attachment: axis-1.3.pom.patch Please use this second attached patch. The first was missing the javax.activation which I don't use but somebody might. > AXIS 1.3 is missing dependencies > > > Key: MEV-192 > URL: http://jira.codehaus.org/browse/MEV-192 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: axis-1.3.pom.patch, axis-1.3.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-192) AXIS 1.3 is missing dependencies
AXIS 1.3 is missing dependencies Key: MEV-192 URL: http://jira.codehaus.org/browse/MEV-192 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Tomislav Stojcevich Attachments: axis-1.3.pom.patch -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-192) AXIS 1.3 is missing dependencies
[ http://jira.codehaus.org/browse/MEV-192?page=all ] Tomislav Stojcevich updated MEV-192: Attachment: axis-1.3.pom.patch Here is the patch file with the dependencies. > AXIS 1.3 is missing dependencies > > > Key: MEV-192 > URL: http://jira.codehaus.org/browse/MEV-192 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Attachments: axis-1.3.pom.patch > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich closed MEV-177: --- Resolution: Fixed > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: MEV-177-jstl.jstl.patch, jstl-1.0.1.pom, jstl-1.0.2.pom, > jstl-1.0.3.pom, jstl-1.0.4.pom, jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, > jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=comments#action_50272 ] Tomislav Stojcevich commented on MEV-177: - It seems to be ok now. The old version must have been cached somewhere or the mirrors had sync issue or something. > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: MEV-177-jstl.jstl.patch, jstl-1.0.1.pom, jstl-1.0.2.pom, > jstl-1.0.3.pom, jstl-1.0.4.pom, jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, > jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich reopened MEV-177: - It looks like all of them got updated except for the 1.0.2 version It's timestamp changed like all the rest but the change is not in it. That's the one that actually effects me. > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: MEV-177-jstl.jstl.patch, jstl-1.0.1.pom, jstl-1.0.2.pom, > jstl-1.0.3.pom, jstl-1.0.4.pom, jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, > jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: MEV-177-jstl.jstl.patch Just found your repository for the poms. Attached is the patch file to make it easier. > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: MEV-177-jstl.jstl.patch, jstl-1.0.1.pom, jstl-1.0.2.pom, > jstl-1.0.3.pom, jstl-1.0.4.pom, jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, > jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: jstl-1.0.5.pom jstl-1.0.4.pom jstl-1.0.3.pom > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Attachments: jstl-1.0.1.pom, jstl-1.0.2.pom, jstl-1.0.3.pom, jstl-1.0.4.pom, > jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: jstl-1.1.1.pom jstl-1.1.0.pom > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Attachments: jstl-1.0.1.pom, jstl-1.0.2.pom, jstl-1.0.3.pom, jstl-1.0.4.pom, > jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: jstl-1.0.2.pom > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Attachments: jstl-1.0.1.pom, jstl-1.0.2.pom, jstl-1.0.3.pom, jstl-1.0.4.pom, > jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: jstl-1.0.1.pom > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Attachments: jstl-1.0.1.pom, jstl-1.0.2.pom, jstl-1.0.3.pom, jstl-1.0.4.pom, > jstl-1.0.5.pom, jstl-1.0.pom, jstl-1.1.0.pom, jstl-1.1.1.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-177) older jstl jars in old location need relocation tag added
[ http://jira.codehaus.org/browse/MEV-177?page=all ] Tomislav Stojcevich updated MEV-177: Attachment: jstl-1.0.pom > older jstl jars in old location need relocation tag added > - > > Key: MEV-177 > URL: http://jira.codehaus.org/browse/MEV-177 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Tomislav Stojcevich > Attachments: jstl-1.0.pom > > > The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a > warning. > All older versions need to have the tag added as well. > The tag needs to be added because in one of my projects I am using the new > groupId (javax.servlet), but some of the transient dependencies are declared > with the older groupId (jstl.jstl). > In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient > dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get > put in my classpath (and in my WEB-INF/lib) with the older one first (since > it sorts that way alphabetically) which is not desirable. If they had the > same groupId maven would use the new one only. > Attached are the updated poms for all older versions with the relocation tag > to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-177) older jstl jars in old location need relocation tag added
older jstl jars in old location need relocation tag added - Key: MEV-177 URL: http://jira.codehaus.org/browse/MEV-177 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Tomislav Stojcevich Attachments: jstl-1.0.pom The 2 newest versions (1.0.6 and 1.1.2) have the relocation tag to give a warning. All older versions need to have the tag added as well. The tag needs to be added because in one of my projects I am using the new groupId (javax.servlet), but some of the transient dependencies are declared with the older groupId (jstl.jstl). In my project I use javax.servlet.jstl-1.0.6.jar, I have a transient dependency that uses jstl.jstl-1.0.2.jar. The result is that both jars get put in my classpath (and in my WEB-INF/lib) with the older one first (since it sorts that way alphabetically) which is not desirable. If they had the same groupId maven would use the new one only. Attached are the updated poms for all older versions with the relocation tag to give the warning. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-145) struts-menu invalid dependencies for m2
[ http://jira.codehaus.org/browse/MEV-145?page=all ] Tomislav Stojcevich updated MEV-145: Attachment: struts-menu-2.3.pom Oops, typo in the first upload, please use this one. Thanks. > struts-menu invalid dependencies for m2 > --- > > Key: MEV-145 > URL: http://jira.codehaus.org/browse/MEV-145 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: struts-menu-2.3.pom, struts-menu-2.3.pom > > > In the junit dependency change to > In velocity-tools dep needs to have view- removed from the version and added > to the end of the artifact-id: velocity-tools-view > servletapi shuld have a scope of provided so it is not packaged in the war -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MEV-145) struts-menu invalid dependencies for m2
[ http://jira.codehaus.org/browse/MEV-145?page=all ] Tomislav Stojcevich reopened MEV-145: - You missed the velocity-tools-view fix change and the scope of provided for servletapi. Attached is the updated pom file. I also changed the groupId for jstl and servlet-api since they were moved in the repository. > struts-menu invalid dependencies for m2 > --- > > Key: MEV-145 > URL: http://jira.codehaus.org/browse/MEV-145 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: struts-menu-2.3.pom > > > In the junit dependency change to > In velocity-tools dep needs to have view- removed from the version and added > to the end of the artifact-id: velocity-tools-view > servletapi shuld have a scope of provided so it is not packaged in the war -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-145) struts-menu invalid dependencies for m2
[ http://jira.codehaus.org/browse/MEV-145?page=all ] Tomislav Stojcevich updated MEV-145: Attachment: struts-menu-2.3.pom > struts-menu invalid dependencies for m2 > --- > > Key: MEV-145 > URL: http://jira.codehaus.org/browse/MEV-145 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Tomislav Stojcevich > Assignee: Edwin Punzalan > Attachments: struts-menu-2.3.pom > > > In the junit dependency change to > In velocity-tools dep needs to have view- removed from the version and added > to the end of the artifact-id: velocity-tools-view > servletapi shuld have a scope of provided so it is not packaged in the war -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1402) application.xml generated incorrectly
[ http://jira.codehaus.org/browse/MNG-1402?page=comments#action_49921 ] Tomislav Stojcevich commented on MNG-1402: -- It does look like they switchd the order. http://java.sun.com/dtd/application_1_3.dtd shows: http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd which is included in http://java.sun.com/xml/ns/j2ee/application_1_4.xsd shows Attached is the new patch that checks for the version and writes them out appropriately. I generated both and both validated correctly. > application.xml generated incorrectly > - > > Key: MNG-1402 > URL: http://jira.codehaus.org/browse/MNG-1402 > Project: Maven 2 > Type: Bug > Components: maven-ear-plugin > Versions: 2.0 > Reporter: Tomislav Stojcevich > Priority: Minor > Attachments: MNG-1402-maven-ear-plugin.patch, > MNG-1402-maven-ear-pluginB.patch > > > When generating an application.xml the description is written out before the > display-name. > According to the DTD, display-name needs to be first. See: > http://java.sun.com/dtd/application_1_3.dtd > A work around is to not use a description element in the pom. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1402) application.xml generated incorrectly
[ http://jira.codehaus.org/browse/MNG-1402?page=all ] Tomislav Stojcevich updated MNG-1402: - Attachment: MNG-1402-maven-ear-pluginB.patch > application.xml generated incorrectly > - > > Key: MNG-1402 > URL: http://jira.codehaus.org/browse/MNG-1402 > Project: Maven 2 > Type: Bug > Components: maven-ear-plugin > Versions: 2.0 > Reporter: Tomislav Stojcevich > Priority: Minor > Attachments: MNG-1402-maven-ear-plugin.patch, > MNG-1402-maven-ear-pluginB.patch > > > When generating an application.xml the description is written out before the > display-name. > According to the DTD, display-name needs to be first. See: > http://java.sun.com/dtd/application_1_3.dtd > A work around is to not use a description element in the pom. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1403) Add on option to include optional dependencies instead of (or in addition to) excluding optional dependencies
Add on option to include optional dependencies instead of (or in addition to) excluding optional dependencies - Key: MNG-1403 URL: http://jira.codehaus.org/browse/MNG-1403 Project: Maven 2 Type: Improvement Versions: 2.0 Reporter: Tomislav Stojcevich Priority: Minor It seems backwards to have to exclude optional dependencies. If I have to declare a dependency, then I am more likely to know which of it's optional dependencies that I need to include, rather than knowing which to exclude. This would greatly reduce (and even eliminate) the number of excludes that are required in my poms. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1402) application.xml generated incorrectly
[ http://jira.codehaus.org/browse/MNG-1402?page=all ] Tomislav Stojcevich updated MNG-1402: - Attachment: MNG-1402-maven-ear-plugin.patch Attached is the patch file. > application.xml generated incorrectly > - > > Key: MNG-1402 > URL: http://jira.codehaus.org/browse/MNG-1402 > Project: Maven 2 > Type: Bug > Components: maven-ear-plugin > Versions: 2.0 > Reporter: Tomislav Stojcevich > Priority: Minor > Attachments: MNG-1402-maven-ear-plugin.patch > > > When generating an application.xml the description is written out before the > display-name. > According to the DTD, display-name needs to be first. See: > http://java.sun.com/dtd/application_1_3.dtd > A work around is to not use a description element in the pom. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1402) application.xml generated incorrectly
application.xml generated incorrectly - Key: MNG-1402 URL: http://jira.codehaus.org/browse/MNG-1402 Project: Maven 2 Type: Bug Components: maven-ear-plugin Versions: 2.0 Reporter: Tomislav Stojcevich Priority: Minor When generating an application.xml the description is written out before the display-name. According to the DTD, display-name needs to be first. See: http://java.sun.com/dtd/application_1_3.dtd A work around is to not use a description element in the pom. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-145) struts-menu invalid dependencies for m2
struts-menu invalid dependencies for m2 --- Key: MEV-145 URL: http://jira.codehaus.org/browse/MEV-145 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Tomislav Stojcevich In the junit dependency change to In velocity-tools dep needs to have view- removed from the version and added to the end of the artifact-id: velocity-tools-view servletapi shuld have a scope of provided so it is not packaged in the war -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
