[jira] Commented: (MDEPLOY-19) Ability to deploy-file as classifier

2006-06-28 Thread Stefan H?bner (JIRA)
[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_68444 ] 

Stefan Hübner commented on MDEPLOY-19:
--

Was there any particular reason, to issue this only for the deploy-file goal? 
Doesn't this also make sense for the deploy-goal?

 Ability to deploy-file as classifier
 

  Key: MDEPLOY-19
  URL: http://jira.codehaus.org/browse/MDEPLOY-19
  Project: Maven 2.x Deploy Plugin
 Type: New Feature

 Versions: 2.1
  Environment: xp
 Reporter: Dan Tran
 Assignee: Allan Ramirez
  Fix For: 2.2
  Attachments: MDEPLOY19.diff

   Time Spent: 2 hours
Remaining: 0 minutes

 deploy-file currently does not support this option

-- 
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: (MRELEASE-122) Versionless Extension causes NullPointerException in release:prepare

2006-05-28 Thread Stefan H?bner (JIRA)
Versionless Extension causes NullPointerException in release:prepare


 Key: MRELEASE-122
 URL: http://jira.codehaus.org/browse/MRELEASE-122
 Project: Maven 2.x Release Plugin
Type: Bug

Versions: 2.0-beta-4
Reporter: Stefan Hübner


I'm getting a NullPointerException when invoking mvn release:prepare
-DdryRun=true (don't know, if the dryRun-parameter makes any
difference). See the stack trace below.

My POM does make use of the wagon-ssh-extension, but without declaring a 
certain version of that extension - which is not necessary, as far as I know.

A workaround to this is to declare a version to the extension.

See this mail thread for a discussion on this issue: 
http://www.nabble.com/NullPointerException+in+Release+Plugin+2.0-beta-4-t1637385.html#a4434481


Stefan


ava.lang.NullPointerException 
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.updateDomVersion(AbstractRewritePomsPhase.java:388)
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.rewriteExtensions(AbstractRewritePomsPhase.java:352)
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:230)
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:165)
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:102)
   at 
org.apache.maven.plugins.release.phase.AbstractRewritePomsPhase.simulate(AbstractRewritePomsPhase.java:529)
   at 
org.apache.maven.plugins.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:135)

-- 
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-2254) the encoding parameter in xml declaration of POM is ignored

2006-05-09 Thread Stefan H?bner (JIRA)
[ http://jira.codehaus.org/browse/MNG-2254?page=comments#action_65078 ] 

Stefan Hübner commented on MNG-2254:


As I just stated in MNG-2255 I think, that ??...the parser used to read in 
maven's model isn't the problem really. It's more likely the way the POM is 
handed to the parser.??

See MNG-2255 for full discussion of the issue.

 the encoding parameter in xml declaration of POM is ignored 
 

  Key: MNG-2254
  URL: http://jira.codehaus.org/browse/MNG-2254
  Project: Maven 2
 Type: Bug

 Reporter: Naoki Nose
  Attachments: DefaultMavenProjectBuilder.diff, modello-plugin-xpp3.diff


 DefaultMavenProjectBuilder reads POM in system default character encoding, 
 and the encoding parameter in xml declartion is ignored.
 to fix this problem, We should
 -  fix  modello-plugin-xpp3 to use the xml parser which is able to handle the 
 encoding parameter properly
 - regenerate maven-model using fixed modello-plugin-xpp3
 - fix DefaultMavenProjectBuilder to use regenerated maven-model properly.

-- 
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