[jira] Updated: (MWAR-169) NPE during packaging.
[ http://jira.codehaus.org/browse/MWAR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MWAR-169: - Fix Version/s: 2.1 Nice bug hunting :) > NPE during packaging. > - > > Key: MWAR-169 > URL: http://jira.codehaus.org/browse/MWAR-169 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-2 >Reporter: Maarten Billemont >Assignee: Stephane Nicoll > Fix For: 2.1 > > > The following NPE happens when I run maven from the parent in a multi-module > project; though it does not occur when I run mvn clean install from within > the module itself. > [INFO] [war:war] > [INFO] Packaging webapp > [INFO] Assembling webapp[safe-online-startup-runtime] in > [/Users/mbillemo/Documents/workspace/safe-online/safe-online-startup-runtime/target/safe-online-startup- > runtime-1.1-SNAPSHOT] > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109) > at > org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288) > at > org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)at > org.apache.maven.cli.MavenCli.main(MavenCli.java:287)at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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
Path for Output of Automated Build should be dynamic based on Build Date and Time
Hi folks i have build a project by using maven. it contains many modules in it. i am facing a problem like not able to make dynamic build path based on build date and time... for entire project build i want the build path to take date and time at which build started.. i have tried by specifying get date and get time in parent POM... but all the individual modules started inheriting this function and each individual module has different folder structure, based on the time at which they started... I want only one main dynamic build path where every module gets deployed in it. i am stuck with this issue for a long time... please suggest me how to overcome this issue thanks in advance... regards nattu -- View this message in context: http://www.nabble.com/Path-for-Output-of-Automated-Build-should-be-dynamic-based-on-Build-Date-and-Time-tp19392788p19392788.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Commented: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147455#action_147455 ] David J. M. Karlsen commented on MECLIPSE-200: -- Is the site staged anywhere (to be able to see documentation of new parameters) > Please add support for the AJDT plugin > -- > > Key: MECLIPSE-200 > URL: http://jira.codehaus.org/browse/MECLIPSE-200 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: AJDT support >Affects Versions: 2.2 >Reporter: Eric Berry >Assignee: Arnaud Heritier > Fix For: 2.6 > > Attachments: ajdt.patch, maven-eclipse-plugin.zip, > maven-eclipse-plugin.zip > > > Please add support for the AJDT plugin. > I have modified the eclipse plugin for our site with the needed changes. I > have attached the modifications that I made for someone to look at and > incorporate into the plugin. -- 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: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too
[ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147477#action_147477 ] Brandon Goodin commented on MDEPLOY-48: --- http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html Deploying Source Jars To deploy a 3rd party source jar, packaging should be set to java-source, and generatePom should be set to false. Works for me:) > deploy:deploy-file does not support deploying sources jars too > -- > > Key: MDEPLOY-48 > URL: http://jira.codehaus.org/browse/MDEPLOY-48 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Geoffrey De Smet > > deploy:deploy does, but deploy:deploy-file doesn't have a parameter to tell > him where the sources jar is: > mvn deploy:deploy-file -Dfile=$artifactFile -DpomFile=$pomFile -Durl=$toRepo -- 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: (MNG-3662) Ampersand in Windows username problem
[
http://jira.codehaus.org/browse/MNG-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147484#action_147484
]
Benjamin Bentmann commented on MNG-3662:
>From a mail Artur sent me today I got this snippet from his POM (I asked him
>to attach it here for further inspection, too):
{code:xml}
{code}
IIRC, the POM is parsed once, then serialized back into a string, this string
is then interpolated and the result is parsed again into a Maven model.
Apparently during serialization into string form, the original CDATA section
markers are lost such that the second parsing step after interpolation is
sensitive to XML metacharacters.
I am too familar with the POM interpolation but maybe we could just make the
MavenXpp3Writer always wrap text with CDATA sections (if requested via some
flag). This way, the interpolator doesn't need to care about XML escaping but
can safely insert replacement values for the expressions.
> Ampersand in Windows username problem
> -
>
> Key: MNG-3662
> URL: http://jira.codehaus.org/browse/MNG-3662
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 2.0.9
> Environment: Windows Vista Small Business
>Reporter: Artur Smiejowski
> Fix For: 2.0.11
>
> Attachments: escape-shell-chars.patch
>
>
> Halo!
> Maven don't work when In Windows user has ampersand in the name for example
> username=Tom&Jerry. Windows allows usernames like this, but Maven treat
> ampersand in the name of users main folder as a part of some url (?) or
> something ... and cannot get path properly. Windows do not allow to change
> username with all user's foldernames.
> Artur
--
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: (MNG-3662) Ampersand in Windows username problem
[
http://jira.codehaus.org/browse/MNG-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147484#action_147484
]
bentmann edited comment on MNG-3662 at 9/9/08 4:01 PM:
>From a mail Artur sent me today I got this snippet from his POM (I asked him
>to attach it here for further inspection, too):
{code:xml}
{code}
IIRC, the POM is parsed once, then serialized back into a string, this string
is then interpolated and the result is parsed again into a Maven model.
Apparently during serialization into string form, the original CDATA section
markers are lost such that the second parsing step after interpolation is
sensitive to XML metacharacters.
I am not familar with the POM interpolation but maybe we could just make the
MavenXpp3Writer always wrap text with CDATA sections (if requested via some
flag). This way, the interpolator doesn't need to care about XML escaping but
can safely insert replacement values for the expressions.
was (Author: bentmann):
From a mail Artur sent me today I got this snippet from his POM (I asked
him to attach it here for further inspection, too):
{code:xml}
{code}
IIRC, the POM is parsed once, then serialized back into a string, this string
is then interpolated and the result is parsed again into a Maven model.
Apparently during serialization into string form, the original CDATA section
markers are lost such that the second parsing step after interpolation is
sensitive to XML metacharacters.
I am too familar with the POM interpolation but maybe we could just make the
MavenXpp3Writer always wrap text with CDATA sections (if requested via some
flag). This way, the interpolator doesn't need to care about XML escaping but
can safely insert replacement values for the expressions.
> Ampersand in Windows username problem
> -
>
> Key: MNG-3662
> URL: http://jira.codehaus.org/browse/MNG-3662
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 2.0.9
> Environment: Windows Vista Small Business
>Reporter: Artur Smiejowski
> Fix For: 2.0.11
>
> Attachments: escape-shell-chars.patch
>
>
> Halo!
> Maven don't work when In Windows user has ampersand in the name for example
> username=Tom&Jerry. Windows allows usernames like this, but Maven treat
> ampersand in the name of users main folder as a part of some url (?) or
> something ... and cannot get path properly. Windows do not allow to change
> username with all user's foldernames.
> Artur
--
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-3748) settings builder doesn't use strict mode in xml parser
settings builder doesn't use strict mode in xml parser -- Key: MNG-3748 URL: http://jira.codehaus.org/browse/MNG-3748 Project: Maven 2 Issue Type: Bug Components: Settings Affects Versions: 2.1.0-M1 Reporter: John Casey Priority: Critical Fix For: 2.1.0-M1 if I leave the repositories/pluginRepositories declarations outside of a profile in the settings.xml file, the latest maven 2.1.0-M1 RC (RC16) *does not* throw an error. -- 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-3748) settings builder doesn't use strict mode in xml parser
[ http://jira.codehaus.org/browse/MNG-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3748: Assignee: John Casey Fix Version/s: 2.1.0-M1 > settings builder doesn't use strict mode in xml parser > -- > > Key: MNG-3748 > URL: http://jira.codehaus.org/browse/MNG-3748 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Critical > Fix For: 2.1.0-M1 > > > if I leave the repositories/pluginRepositories declarations outside of a > profile in the settings.xml file, the latest maven 2.1.0-M1 RC (RC16) *does > not* throw an error. -- 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: (MSITE-30) site:deploy incompatibilities with m1.02
[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147488#action_147488 ] Dennis Lundberg commented on MSITE-30: -- We are talking about a major version upgrade here and all features from a previous version may not there in the new version, especially if it is a major rewrite as it is in this case. In my book the definition of a bug is: "A feature that is designed to be in the software. When that feature does not work as designed it's a bug." That's the reason for me to change the type for this issue. > site:deploy incompatibilities with m1.02 > > > Key: MSITE-30 > URL: http://jira.codehaus.org/browse/MSITE-30 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site:deploy > Environment: All >Reporter: Paul Spencer > Fix For: 2.0-beta-8 > > > Deploying a site in m2 has changed since m1. > 1) m1 used the "tar" and "gunzip" command on the remote site, where m2 uses > the "unzip" command. This poses a problem for be since my remote site does > not support the "unzip" command, thus making the "priority" of this issue > major > 1.1) Their may be desire to deploy without the use of tools like tar and zip > on some site. The deploy would esentailly be a recersive copy > 2) No equivelent to m1 property maven.site.chmod.mode. I use this to allow > other member is the group update and delete permission > 3) No equivelent to m1 property maven.site.publish.clean > Their are other properties for the m1.02 not mentioned above, but I suspect > the they can be calculated from m2 files, i.e. pom.xml and settings.xml. > Paul Spencer -- 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: (MRELEASE-295) Internal dependencies left at old snapshot
[
http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147489#action_147489
]
Trenton commented on MRELEASE-295:
--
I am having the same issue. It happens on a dependency of a profile within the
pom.
For example, after a dryRun, I have the following...
web/pom.xml.tag
inproc
true
true
${basedir}/src/main/resources
ca.athabascau.banner.oros
rmi
1.2.0-SNAPSHOT
compile
> Internal dependencies left at old snapshot
> --
>
> Key: MRELEASE-295
> URL: http://jira.codehaus.org/browse/MRELEASE-295
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
>Reporter: Chris Searle
> Attachments: release_test.zip
>
>
> I'm having a problem with version numbering when releasing a given reactor
> with modules within the reactor that have dependencies inside the reactor.
> I have narrowed this to the following structure
> A parent test/pom.xml (basically a pom packging grouping pom - but here is
> where the scm and repos are also defined) with
> test
> test
> pom
> 1.0-SNAPSHOT
> and
>
> test-1
> test-2
>
> Then - the two modules:
> test/test-1/pom.xml with
>
> test
> test
> 1.0-SNAPSHOT
>
> test
> test-1
> 1.0-SNAPSHOT
> test/test-2/pom.xml with
>
> test
> test
> 1.0-SNAPSHOT
>
> test
> test-2
> 1.0-SNAPSHOT
>
>
> test
> test-1
> 1.0-SNAPSHOT
>
>
> Then run mvn -DdryRun=true release:prepare
> test/pom.xml.tag version=1.0 - good
> test/pom.xml.next version=1.1-SNAPSHOT - good
> test-1/pom.xml.tag version=1.0, parent version=1.0 good
> test-1/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> test-2/pom.xml.tag version=1.0, parent version=1.0, dependency to test-1
> version=1.0 good
> test-2/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> BUT
> test-2/pom.xml.next dependency to test-1 version=1.0-SNAPSHOT
> This seems wrong to me - I would expect it to also get 1.1-SNAPSHOT for the
> dependency on test-1 since it has the same parent and is being run in the
> same reactor.
--
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: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147491#action_147491 ] Arnaud Heritier commented on MECLIPSE-200: -- It will be in few hours here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.6-SNAPSHOT/ > Please add support for the AJDT plugin > -- > > Key: MECLIPSE-200 > URL: http://jira.codehaus.org/browse/MECLIPSE-200 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: AJDT support >Affects Versions: 2.2 >Reporter: Eric Berry >Assignee: Arnaud Heritier > Fix For: 2.6 > > Attachments: ajdt.patch, maven-eclipse-plugin.zip, > maven-eclipse-plugin.zip > > > Please add support for the AJDT plugin. > I have modified the eclipse plugin for our site with the needed changes. I > have attached the modifications that I made for someone to look at and > incorporate into the plugin. -- 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-3748) settings builder doesn't use strict mode in xml parser
[ http://jira.codehaus.org/browse/MNG-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3748. --- Resolution: Fixed fixed this by rolling back to alpha-13 of the modello plugin. In the longer run, modello will need to be fixed and re-released. > settings builder doesn't use strict mode in xml parser > -- > > Key: MNG-3748 > URL: http://jira.codehaus.org/browse/MNG-3748 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Critical > Fix For: 2.1.0-M1 > > > if I leave the repositories/pluginRepositories declarations outside of a > profile in the settings.xml file, the latest maven 2.1.0-M1 RC (RC16) *does > not* throw an error. -- 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-3749) Install kills Eclipse on Ubuntu; too many files open.
Install kills Eclipse on Ubuntu; too many files open. - Key: MNG-3749 URL: http://jira.codehaus.org/browse/MNG-3749 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Environment: Ubuntu/Debian/Linux 2.6.24-19-generic kernel; Eclipse Ganymede Reporter: James D Carroll Installed latest version from update site and immediately began getting errors such all premised on 'too many files open'. Its broken so bad I can't even get into the system info or try to uninstall the thing. -- 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: (MNG-3749) Install kills Eclipse on Ubuntu; too many files open.
[ http://jira.codehaus.org/browse/MNG-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147504#action_147504 ] Ralph Goers commented on MNG-3749: -- Maybe its just me, but I don't understand the problem description. Are you saying you installed Maven and immediately got "too many file open" without even running maven? If not then can you provide a more detailed description of what the problem is? > Install kills Eclipse on Ubuntu; too many files open. > - > > Key: MNG-3749 > URL: http://jira.codehaus.org/browse/MNG-3749 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 > Environment: Ubuntu/Debian/Linux 2.6.24-19-generic kernel; Eclipse > Ganymede >Reporter: James D Carroll > > Installed latest version from update site and immediately began getting > errors such all premised on 'too many files open'. Its broken so bad I can't > even get into the system info or try to uninstall the thing. -- 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: (ARCHETYPE-203) resources file don't copy to the proper location
resources file don't copy to the proper location - Key: ARCHETYPE-203 URL: http://jira.codehaus.org/browse/ARCHETYPE-203 Project: Maven Archetype Issue Type: Bug Components: Archetypes Environment: Win XP Eclipse Version: 3.4.0 Build id: I20080617-2000 Reporter: Ching Yi, Chan I make an archetype plugin. when I use maven in command line my resources file will locate as package structure with archetype:generate but archetype:create will not. I test it in eclipse with m2e plugin, files in the resources are all in the root directory of resources. how do I make it locate as package structure ? -- 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: (ARCHETYPE-203) resources file don't copy to the proper location
[ http://jira.codehaus.org/browse/ARCHETYPE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147505#action_147505 ] Ching Yi, Chan commented on ARCHETYPE-203: -- I issue it on maillist, Eugene suggested I can post problem here [quote] m2eclipse actually is not calling either of those goals. It is directly working with archetype-common component. Please report issue about resources to the Archetype project at http://jira.codehaus.org/browse/ARCHETYPE regards, Eugene [/quote] > resources file don't copy to the proper location > - > > Key: ARCHETYPE-203 > URL: http://jira.codehaus.org/browse/ARCHETYPE-203 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes > Environment: Win XP > Eclipse > Version: 3.4.0 > Build id: I20080617-2000 >Reporter: Ching Yi, Chan > > I make an archetype plugin. > when I use maven in command line my resources file will locate as > package structure with archetype:generate but archetype:create will not. > I test it in eclipse with m2e plugin, files in the resources are all in > the root directory of resources. how do I make it locate as package > structure ? -- 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-3750) Artifact version is downloaded even if excluded or omitted for nearer
Artifact version is downloaded even if excluded or omitted for nearer - Key: MNG-3750 URL: http://jira.codehaus.org/browse/MNG-3750 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.9 Environment: any Reporter: Bernhard Seebass mvn downloads artifact versions, even if they are excluded or omitted for nearer. This is a real problem, if the artifact version in question is a SNAPSHOT version that is no more available. Example debug output (from eclipse): Unable to get resource 'commons-dbutils:commons-dbutils:pom:20060830' from repository central (http://repo1.maven.org/maven2) Unable to locate resource in repository testArtifact: artifact=commons-dbutils:commons-dbutils:jar:20060830:compile omitForNearer: omitted=commons-dbutils:commons-dbutils:jar:20060830:compile kept=commons-dbutils:commons-dbutils:jar:1.1:compile -- 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: (DOXIA-185) Add encoding support
[
http://jira.codehaus.org/browse/DOXIA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147507#action_147507
]
Vincent Siveton commented on DOXIA-185:
---
Lukas, the only need that I see is for xml files and specially for XhtmlSink.
We need to find a way to add:
{noformat}
{noformat}
and
{noformat}
{noformat}
> Add encoding support
>
>
> Key: DOXIA-185
> URL: http://jira.codehaus.org/browse/DOXIA-185
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Sink API
>Affects Versions: 1.0-alpha-10
>Reporter: Vincent Siveton
>
--
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: (SCM-318) Allow tags to be removed
[ http://jira.codehaus.org/browse/SCM-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147510#action_147510 ] Tim Jones commented on SCM-318: --- Are there any plans to address this issue? > Allow tags to be removed > > > Key: SCM-318 > URL: http://jira.codehaus.org/browse/SCM-318 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Affects Versions: 1.0-rc1 >Reporter: Mark Hobson > Fix For: 1.x > > > Need to add an untag or removeTag method to ScmProvider to reverse the tag > operation. -- 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
