date:20071017


 [ 
http://jira.codehaus.org/browse/MNG-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MNG-2254.
--

  Assignee: Herve Boutemy  (was: Jason van Zyl)
Resolution: Fixed

work done:
- r585265 for trunk
- r585268 for 2.0.x branch

 the encoding parameter in xml declaration of POM is ignored 
 

 Key: MNG-2254
 URL: http://jira.codehaus.org/browse/MNG-2254
 Project: Maven 2
  Issue Type: Bug
  Components: POM::Encoding
Reporter: Naoki Nose
Assignee: Herve Boutemy
 Fix For: 2.0.8

 Attachments: DefaultMavenProjectBuilder.diff, MNG-2254-2.diff, 
 mng-2254-PomEncoding.tgz, MNG-2254.diff, MNG-2254_artifact.diff, 
 MNG-2254_components-new.diff, MNG-2254_components.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

[jira] Updated: (MWAR-124) accept packaging task passed by other plugin via the plugin context

2007-10-17 Thread nicolas de loof (JIRA)


 [ 
http://jira.codehaus.org/browse/MWAR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

nicolas de loof updated MWAR-124:
-

Attachment: war-plugin-external-packaging-tasks.patch

Reworked pacth to avoid NullPointers in unit tests.

 accept packaging task passed by other plugin via the plugin context
 ---

 Key: MWAR-124
 URL: http://jira.codehaus.org/browse/MWAR-124
 Project: Maven 2.x War Plugin
  Issue Type: Improvement
Reporter: nicolas de loof
Assignee: Stephane Nicoll
Priority: Trivial
 Attachments: war-plugin-external-packaging-tasks.patch, 
 war-plugin-external-packaging-tasks.patch


 In maven 2.0.x there is no phase beetween creating the exploded artifact to 
 be packaged and packaging as an archive. my javascript plugins needs to 
 assemble source files into the webapp root /scripts directory. The only way 
 today is to run during the test phase, to ensure runing prior the war plugin.
 The WarPackagingTask is an abstration that could allow other plugins to 
 register some tasks to perform during the exploded webapp creation. As the 
 pluginContext is desinged to help plugins share datas, it can be used to pass 
 custom packaginTask (and postPackagin ones) to the war plugin from another 
 plugin.
 The attached patch adds two constants to define suchentries in the context 
 and teh required code to get them and add the to the packaging and 
 post-packaging tasks lists.

-- 
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: (MRM-536) JVM Bug Triggered in archiva-metadata-reports


 [ 
http://jira.codehaus.org/browse/MRM-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter closed MRM-536.


  Assignee: Brett Porter
Resolution: Won't Fix

re-open if you have an answer to the above

 JVM Bug Triggered in archiva-metadata-reports
 -

 Key: MRM-536
 URL: http://jira.codehaus.org/browse/MRM-536
 Project: Archiva
  Issue Type: Bug
  Components: build
Affects Versions: 1.0-beta-3
Reporter: Joakim Erdfelt
Assignee: Brett Porter
 Attachments: hs_err_pid30832.log


 {noformat}
 ---
  T E S T S
 ---
 There are no tests to run.
 Results :
 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
 [INFO] [jar:jar]
 [INFO] Building jar: 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
 archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
 [INFO] [install:install]
 [INFO] Installing 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
 archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar to 
 /home/joakim/.m2/repository-archiva/org/apache/maven/archiva/archiva-metadata-re
 ports/1.0-beta-3-SNAPSHOT/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
 [INFO] 
 
 [INFO] Building Archiva Reporting :: Project Reports
 [INFO]task-segment: [clean, install]
 [INFO] 
 
 [INFO] [clean:clean]
 [INFO] Deleting directory 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target
 [INFO] Deleting directory 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/classes
 [INFO] Deleting directory 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/test-classes
 [INFO] Deleting directory 
 /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/site
 [INFO] [plexus:descriptor {execution: generate}]
 [INFO] [remote-resources:process {execution: default}]
 [INFO] [resources:resources]
 [INFO] Using default encoding to copy filtered resources.
 #
 # An unexpected error has been detected by HotSpot Virtual Machine:
 #
 #  SIGSEGV (0xb) at pc=0xb79a4afd, pid=30832, tid=3085063872
 #
 # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode, sharing)
 # Problematic frame:
 # V  [libjvm.so+0x324afd]
 #
 # An error report file with more information is saved as hs_err_pid30832.log
 #
 # If you would like to submit a bug report, please visit:
 #   http://java.sun.com/webapps/bugreport/crash.jsp
 #
 Aborted (core dumped)
 {noformat}

-- 
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: (MRM-541) convenient way to take Archiva proxies offline


 [ 
http://jira.codehaus.org/browse/MRM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter updated MRM-541:
-

Fix Version/s: Future

 convenient way to take Archiva proxies offline
 

 Key: MRM-541
 URL: http://jira.codehaus.org/browse/MRM-541
 Project: Archiva
  Issue Type: Improvement
  Components: remote proxy
Affects Versions: 1.0-beta-2
Reporter: Brett Porter
 Fix For: Future


 I'm on a bad connection and proxying is very slow, making every archiva 
 request a multiple of that slowness. I don't want to temporarily modify the 
 configuration to disable the connectors (or even to turn on failure caching 
 which would help a little) - but I would like to have an admin feature to 
 temporarily turn off the proxy functionality altogether, considering Archiva 
 offline (but still serving requests, not that kind of offline :).

-- 
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: (MRM-545) Documentation for configuring for Tomcat is invalid

[
http://jira.codehaus.org/browse/MRM-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated MRM-545:
-

Fix Version/s: 1.0-beta-4

Documentation for configuring for Tomcat is invalid
---

Key: MRM-545
URL: http://jira.codehaus.org/browse/MRM-545
Project: Archiva
Issue Type: Bug
Components: documentation
Affects Versions: 1.0-beta-2
Environment: Windows XP, Tomcat-5.5.17/Tomcat-5.5.20, JDK-1.5.0_06
Reporter: William Ferguson
Priority: Critical
Fix For: 1.0-beta-4

Attachments: bad-log-filename.log, mail-auth-class-not-found.log

Following http://maven.apache.org/archiva/guides/getting-started.html for
Tomcat didn't get me started.
I'll go through it point by point
# Create a directory in tomcat called archiva, at the same level as bin,
conf, logs and the others.
# Copy the war file from apps/archiva/lib into the new directory
There is not apps/archiva/lib in the 1.0-beta-2 distribution.
apps contains a single file : archiva-plexus-application-1.0-beta-2.jar which
does itself contain a war file, so I extracted that file and copied it to the
TOMCAT_HOME/archiva folder.
NB IMHO modifying TOMCAT in this manner smells all wrong.
# Create a conf/Catalina/localhost/archiva.xml file with the following data:
yadda, yadda
The docBase attribute refers to archiva-webapp-1.0-SNAPSHOT.war instead of
archiva-webapp-1.0-beta-2.war
No idea why a javax.mail.Session needs to be configured here, haven't seen
any documentation in Archiva that suggests it send, receives email. But this
was a slight pain when configuring for Tomcat-5.5.20 as I needed to follow
the extra steps for the missing classes. If the MailSession is not required
it would be better to avoid this pain by simplifying the config.
Again modifying TOMCAT like this does not feel right. Surely this config
could be contained within the webapp.
# Copy $HOME/.m2/org/apache/derby/derby/10.1.3.1/derby-10.1.3.1.jar (or from
the remote repository) into the Tomcat common/lib
I am *really* against this as I have now introduced Derby-10.1.3.1 into the
classpath of 8all* my other applications running on that Tomcat instance.
Surely this library could be packaged up into the webapp.
# To deal with a current bug, you'll also need to add the following to your
$catalina.home/conf/web.xml in the relevant section (search for jspx):
Again, surely this could be included in the config for the Archiva webapp
instead of introduced into Tomcat generally. This heavy handed approach makes
maintenance difficult, eg upgrading to a new version of Tomcat is now
extremely onerous.
OK, so having followed the instructions above, when I try to startup Tomcat
the first thin I get is a failure with the logging sub system. see attached
bad-log-filename.log. I believe this is due to the fact that
${appserver.base} in log4j.xml has never been set:
{code}
param name=file value=${appserver.base}/logs/archiva.log /
{code}
Next, it fails as it can't find javax.mail.Authenticator (this is
Tomcat-5.5.17).
NB I never saw any indication that schema SA does not exist as the final
note suggests. But perhaps this was because Archiva never got that far.
Certainly no application is available at http://localhost:8080/archiva/
Anyway, by this stage I became discouraged enough that I gave up.
Its a shame really as I would have liked to be able to compare Archiva
against Proximity and Artifactory, both of which I managed to get setup in
under 10 mins including vastly restructuring the default repository config
that they ship with.
Brett, hope that helps.
Further notes:
I really don't like modifying the contents of TOMCAT_HOME other than to
deploy a WAR to TOMCAT_HOME/webapps.
And the infrastructure team weren't impressed either and its makes
maintenance high cost.
Better to keep all config solely within the confines of the webapp or use a
environment variable to declare a separate proxy_home where all the config is
contained (like Artifactory does).

--
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: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.


 [ 
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter updated MRM-523:
-

 Priority: Minor  (was: Major)
Fix Version/s: (was: 1.0-beta-3)
   1.x

not critical.

it's just a local repository assumption (we should instead pass in a repository 
to store in) - there are other points in archiva that use user.home and would 
be similarly affected



 Appearance Actions do not work when ${user.home} is invalid.
 

 Key: MRM-523
 URL: http://jira.codehaus.org/browse/MRM-523
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
 Fix For: 1.x


 The reliance on maven core components with regards to Appearance / Company 
 Info / Edit Pom actions, prevents server installations without a valid user 
 $HOME directory. ( such as /dev/null )
 We should migrate away from maven core components at our earliest opportunity.

-- 
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] Reopened: (MRM-398) configure guest access by default for pre-configured repositories


 [ 
http://jira.codehaus.org/browse/MRM-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter reopened MRM-398:
--


I found that this isn't working on a clean installation + database:

jvm 1| 2007-10-17 18:21:39,076 [WrapperSimpleAppMain] WARN  
org.apache.maven.archiva.web.startup.SecuritySynchronization:default  - Unable 
to add role [Repository Observer - snapshots] to Guest user.
jvm 1| org.codehaus.plexus.redback.rbac.RbacObjectNotFoundException: Unable 
to find RBAC Object 'Guest' of type 
org.codehaus.plexus.redback.rbac.jdo.JdoUserAssignment using fetch-group 'null'
jvm 1|  at 
org.codehaus.plexus.redback.rbac.jdo.JdoTool.getObjectById(JdoTool.java:316)

...

jvm 1| Caused by: javax.jdo.JDOObjectNotFoundException: No such database row
jvm 1| FailedObject:Guest
jvm 1|  at 
org.jpox.store.rdbms.request.FetchRequest.execute(FetchRequest.java:194)


 configure guest access by default for pre-configured repositories
 -

 Key: MRM-398
 URL: http://jira.codehaus.org/browse/MRM-398
 Project: Archiva
  Issue Type: Bug
  Components: Users/Security
Affects Versions: 1.0-alpha-1
Reporter: Brett Porter
Assignee: Joakim Erdfelt
 Fix For: 1.0-beta-3


 I think it makes sense for repositories to be readable by guests by default 
 for a good OOTB experience.

-- 
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: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.


[ 
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110152
 ] 

Brett Porter commented on MRM-523:
--

a related issue is the creation of ~/.m2/archiva directory for a single 
metadata file during this process.

 Appearance Actions do not work when ${user.home} is invalid.
 

 Key: MRM-523
 URL: http://jira.codehaus.org/browse/MRM-523
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
 Fix For: 1.x


 The reliance on maven core components with regards to Appearance / Company 
 Info / Edit Pom actions, prevents server installations without a valid user 
 $HOME directory. ( such as /dev/null )
 We should migrate away from maven core components at our earliest opportunity.

-- 
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-1524) Continuum don't find the default build definition for ANT/Shell projects

Continuum don't find the default build definition for ANT/Shell projects


 Key: CONTINUUM-1524
 URL: http://jira.codehaus.org/browse/CONTINUUM-1524
 Project: Continuum
  Issue Type: Bug
  Components: Core system, Integration - Ant, Integration - Shell
Affects Versions: 1.1-beta-4
Reporter: Emmanuel Venisse
 Fix For: 1.1-beta-4


Default build def can't be found if it is defined at the project level and the 
user choose to build project with the build project(s) button in the Member 
Project part in the project group summary

-- 
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: (CONTINUUM-1524) Continuum don't find the default build definition for ANT/Shell projects


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Venisse updated CONTINUUM-1524:


Fix Version/s: 1.1-beta-4

 Continuum don't find the default build definition for ANT/Shell projects
 

 Key: CONTINUUM-1524
 URL: http://jira.codehaus.org/browse/CONTINUUM-1524
 Project: Continuum
  Issue Type: Bug
  Components: Core system, Integration - Ant, Integration - Shell
Affects Versions: 1.1-beta-4
Reporter: Emmanuel Venisse
Assignee: Emmanuel Venisse
 Fix For: 1.1-beta-4


 Default build def can't be found if it is defined at the project level and 
 the user choose to build project with the build project(s) button in the 
 Member Project part in the project group summary

-- 
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: (CONTINUUM-1524) Continuum don't find the default build definition for ANT/Shell projects


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Venisse closed CONTINUUM-1524.
---

Resolution: Fixed

Done.

 Continuum don't find the default build definition for ANT/Shell projects
 

 Key: CONTINUUM-1524
 URL: http://jira.codehaus.org/browse/CONTINUUM-1524
 Project: Continuum
  Issue Type: Bug
  Components: Core system, Integration - Ant, Integration - Shell
Affects Versions: 1.1-beta-4
Reporter: Emmanuel Venisse
Assignee: Emmanuel Venisse
 Fix For: 1.1-beta-4


 Default build def can't be found if it is defined at the project level and 
 the user choose to build project with the build project(s) button in the 
 Member Project part in the project group summary

-- 
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-3241) It's not possible to get a property with unescaped sign for urls

It's not possible to get a property with unescaped  sign for urls
--

 Key: MNG-3241
 URL: http://jira.codehaus.org/browse/MNG-3241
 Project: Maven 2
  Issue Type: Bug
Reporter: Nils Eckert


I found no way to create a property with a not escaped ampersand (-sign). This 
is needed for a MySQL jdbc-connection String with some connection variabled and 
should be filtered in a properties file during compile phase.

It tried to escape it with amp; This leeds to following error: Project build 
error Cannot read project model from interpolating filter of serialized version.

It is no option to use a double escaping with amp;amp;. Here I get a amp; in 
my connection url.

I also tried to use a [CDATA[ ... ]] with the same problems. It's not 
possible to use  sign. And if I use amp; this escaped tag appears in my 
properties file after filtering.

-- 
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-3242) It's not possible to get a property with unescaped sign for urls

It's not possible to get a property with unescaped  sign for urls
--

 Key: MNG-3242
 URL: http://jira.codehaus.org/browse/MNG-3242
 Project: Maven 2
  Issue Type: Bug
  Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert


I found no way to create a property with a not escaped ampersand (-sign). This 
is needed for a MySQL jdbc-connection String with some connection variabled and 
should be filtered in a properties file during compile phase.

It tried to escape it with amp; This leeds to following error: Project build 
error Cannot read project model from interpolating filter of serialized version.

It is no option to use a double escaping with amp;amp;. Here I get a amp; in 
my connection url.

I also tried to use a [CDATA[ ... ]] with the same problems. It's not 
possible to use  sign. And if I use amp; this escaped tag appears in my 
properties file after filtering.

-- 
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-3243) It's not possible to get a property with unescaped sign for urlsIt's not possible to get a property with unescaped sign for urls

It's not possible to get a property with unescaped  sign for urlsIt's not 
possible to get a property with unescaped  sign for urls


 Key: MNG-3243
 URL: http://jira.codehaus.org/browse/MNG-3243
 Project: Maven 2
  Issue Type: Bug
  Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert


I found no way to create a property with a not escaped ampersand (-sign). This 
is needed for a MySQL jdbc-connection String with some connection variabled and 
should be filtered in a properties file during compile phase.

It tried to escape it with amp; This leeds to following error: Project build 
error Cannot read project model from interpolating filter of serialized version.

It is no option to use a double escaping with amp;amp;. Here I get a amp; in 
my connection url.

I also tried to use a [CDATA[ ... ]] with the same problems. It's not 
possible to use  sign. And if I use amp; this escaped tag appears in my 
properties file after filtering.

-- 
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-3243) It's not possible to get a property with unescaped sign for urlsIt's not possible to get a property with unescaped sign for urls


 [ 
http://jira.codehaus.org/browse/MNG-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nils Eckert closed MNG-3243.


Resolution: Fixed

Got HTTP 404 with Safari 3.0 and tried again. Double Post.

 It's not possible to get a property with unescaped  sign for urlsIt's not 
 possible to get a property with unescaped  sign for urls
 

 Key: MNG-3243
 URL: http://jira.codehaus.org/browse/MNG-3243
 Project: Maven 2
  Issue Type: Bug
  Components: General
Affects Versions: 2.0.6
Reporter: Nils Eckert

 I found no way to create a property with a not escaped ampersand (-sign). 
 This is needed for a MySQL jdbc-connection String with some connection 
 variabled and should be filtered in a properties file during compile phase.
 It tried to escape it with amp; This leeds to following error: Project build 
 error Cannot read project model from interpolating filter of serialized 
 version.
 It is no option to use a double escaping with amp;amp;. Here I get a amp; 
 in my connection url.
 I also tried to use a [CDATA[ ... ]] with the same problems. It's not 
 possible to use  sign. And if I use amp; this escaped tag appears in my 
 properties file after filtering.

-- 
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-3241) It's not possible to get a property with unescaped sign for urls


 [ 
http://jira.codehaus.org/browse/MNG-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nils Eckert closed MNG-3241.


Resolution: Duplicate

Got HTTP 404 with Safari 3.0 and tried again. Double Post.

 It's not possible to get a property with unescaped  sign for urls
 --

 Key: MNG-3241
 URL: http://jira.codehaus.org/browse/MNG-3241
 Project: Maven 2
  Issue Type: Bug
Reporter: Nils Eckert

 I found no way to create a property with a not escaped ampersand (-sign). 
 This is needed for a MySQL jdbc-connection String with some connection 
 variabled and should be filtered in a properties file during compile phase.
 It tried to escape it with amp; This leeds to following error: Project build 
 error Cannot read project model from interpolating filter of serialized 
 version.
 It is no option to use a double escaping with amp;amp;. Here I get a amp; 
 in my connection url.
 I also tried to use a [CDATA[ ... ]] with the same problems. It's not 
 possible to use  sign. And if I use amp; this escaped tag appears in my 
 properties file after filtering.

-- 
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-2896) ${basedir} used in a repository url does not work for parent pom lookup

2007-10-17 Thread Michele Lorenzini (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110172
 ] 

Michele Lorenzini commented on MNG-2896:


I have a similar problem:
in the settings.xml I define a property, say:

internal.repos.baseurlhttp://myinternalreponame/repos/internal.repos.baseurl

then define a repository using that property, say:
repository
  idmyRepo1/id
  nameMy repo/name
  url${internal.repos.baseurl}/repo1/url
/repository

Now, I have a general parent pom that I have deployed on this repo and a 
project which uses it.
If I try to mvn validate the child project, and I use a clean local 
repository,
maven cannot find the parent pom on the remote repository:

[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: my.groupid:my-parent::1.0 of project: 
my.groupid:my-child:jar:1.0 in relative path: ../pom.xml
[DEBUG] Parent-POM: my.groupid:my-parent::1.0 not found in relative path: 
../pom.xml
[DEBUG] Retrieving parent-POM: my.groupid:my-parent::1.0 for project: 
my.groupid:my-child:jar:1.0 from the repository.
[DEBUG] Trying repository myRepo1
Downloading: 
${internal.repos.baseurl}/repo1/my/groupid/my-parent/1.0/my-parent-1.0.pom
[DEBUG] Unable to get resource 'my.groupid:my-parent::1.0' from repository 
myRepo1 (${internal.repos.baseurl}/repo1)

It seems maven does not resolve the property ${internal.repos.baseurl},
if I put the url directly in the repository definition maven finds and gets the 
parent pom without problems.

The same definition (using the property ${internal.repos.baseurl}) works fine 
for retrieving dependencies
from the remote repository.

So I suppose the problem is only in the parent pom retrieval when a $ property 
is used in the url element
of a repository config.
Hope it helps


 ${basedir} used in a repository url does not work for parent pom lookup
 ---

 Key: MNG-2896
 URL: http://jira.codehaus.org/browse/MNG-2896
 Project: Maven 2
  Issue Type: Wish
  Components: POM
Affects Versions: 2.0.5
Reporter: Stefano Bagnara
 Fix For: Reviewed Pending Version Assignment


 I use something like this to store locally the dependencies.
 -
 repository
   idparent-james-stage-m1/id
   nameJames stage repository/name
   urlfile://${basedir}/stage/url
   layoutlegacy/layout
   releases
 enabledtrue/enabled
 checksumPolicyignore/checksumPolicy
   /releases
   snapshots
 enabledtrue/enabled
 checksumPolicyignore/checksumPolicy
   /snapshots
 /repository
 
 Everything works fine but the parent resolution: my main pom.xml has a parent 
 and it is not looked up in this repository.
 Well, it is lookedup, but ${basedir} is not expanded and this way the lookup 
 does not work.
 If I replace the ${basedir} with my full path everything works fine, but I 
 cannot obviously do that as the local repository is part of the svn tree (by 
 our choice to not use remote repositories).
 Furthermore: is there a variable to be used instead of ${basedir} that always 
 reference to its own pom.xml folder? I ask this because I have multiple 
 modules inside this project and I had to add another repository to this pom 
 using file://${basedir}/../stage (notice the ..) so that submodules will use 
 the same repository for the lookups, but this sound like an hack.

-- 
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: (MPLUGIN-39) adding package-info.java breaks build

2007-10-17 Thread Florian Kleedorfer (JIRA)

adding package-info.java breaks build
-

 Key: MPLUGIN-39
 URL: http://jira.codehaus.org/browse/MPLUGIN-39
 Project: Maven 2.x Plugin Plugin
  Issue Type: Bug
 Environment: Windows XP, Java 5, maven 2.0.7
Reporter: Florian Kleedorfer
Priority: Minor


As soon as I add a package-info.java file to the package of my mojo, the build 
breaks with the following output:

[INFO] [plugin:descriptor]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] 0
[INFO] 
[DEBUG] Trace
java.lang.ArrayIndexOutOfBoundsException: 0
at 
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.getJavaClass(JavaMojoDescriptorExtractor.java:534)
at 
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:553)
at 
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:84)
at 
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:135)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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)
[INFO] 
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Oct 17 11:48:52 CEST 2007
[INFO] Final Memory: 4M/1016M
[INFO] 

-- 
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: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.


[ 
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110179
 ] 

Joakim Erdfelt commented on MRM-523:


Actually, no.

We have mitigated all other ${user.home} situations.
And we have 2 known users now that run Archiva on a Unix environment with a 
homeless user (a common security practice).


 Appearance Actions do not work when ${user.home} is invalid.
 

 Key: MRM-523
 URL: http://jira.codehaus.org/browse/MRM-523
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
 Fix For: 1.x


 The reliance on maven core components with regards to Appearance / Company 
 Info / Edit Pom actions, prevents server installations without a valid user 
 $HOME directory. ( such as /dev/null )
 We should migrate away from maven core components at our earliest opportunity.

-- 
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: (CONTINUUM-1475) 1.1 beta 3 uses the same windows service name with 1.0.3


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Venisse updated CONTINUUM-1475:


Fix Version/s: (was: 1.1-beta-4)
   To Sort

 1.1 beta 3 uses the same windows service name with 1.0.3
 

 Key: CONTINUUM-1475
 URL: http://jira.codehaus.org/browse/CONTINUUM-1475
 Project: Continuum
  Issue Type: Bug
  Components: Environmental
Affects Versions: 1.1-beta-3
 Environment: xp
Reporter: Dan Tran
 Fix For: To Sort


 so user will need to remove 1.0.3 service inorder to install 1.1 beta3

-- 
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: (CONTINUUM-1233) Reduce number of clicks to add a project


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Venisse closed CONTINUUM-1233.
---

Resolution: Fixed

Done.

Wendy, Please open a new issue to remove Maven1/ant project from the list.

 Reduce number of clicks to add a project
 

 Key: CONTINUUM-1233
 URL: http://jira.codehaus.org/browse/CONTINUUM-1233
 Project: Continuum
  Issue Type: Improvement
  Components: Web - UI
Affects Versions: 1.1-alpha-1
Reporter: Wendy Smoak
Assignee: Emmanuel Venisse
 Fix For: 1.1-beta-4


 With the addition of the project group roles, adding a Maven 2 project 
 changed from one click (Add M2 Project button)  to three clicks-- focus on 
 the Add New Project drop-down, select a type, click the Add button.
 If we made the default for the select list configurable somewhere, or even 
 made it remember the last choice used during that session, then adding 
 multiple projects would be much more pleasant.
 In addition, adding a project returns you to the Project Groups page, so that 
 you have to click to get back to the group summary page to add the next 
 project.  (Similar to CONTINUUM-1115)

-- 
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: (MRM-546) Duplicate repositories show up while editing.

Duplicate repositories show up while editing.
-

 Key: MRM-546
 URL: http://jira.codehaus.org/browse/MRM-546
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Priority: Critical


Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to 
1.0-beta-2.
Situation: When editing the repositories, the repositories get duplicated.

This is likely due to the fact that the configuration upgrade technique from 
repositories to managedRepositories and remoteRepositories is not 
removing the repositories section properly..

Several efforts in the code have been made to correct this, but with no 
success. See revision 583903 in archiva/trunk for details.

-- 
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: (MAVENUPLOAD-1763) Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Nyika closed MAVENUPLOAD-1763.
--

Resolution: Fixed

The developer will change the groupId appropriately and then upload the change.

 Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository
 -

 Key: MAVENUPLOAD-1763
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1763
 Project: maven-upload-requests
  Issue Type: New Feature
Reporter: Michael Nyika
 Attachments: maven-grester-plugin-0.3-bundle.jar


 The Grester 0.3 Bundle is a Maven Plugin for Unit Testing. It is used 
 together with Jester and JUnit to test source code. 

-- 
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: (MAVENUPLOAD-1772) Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered)

Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered)


 Key: MAVENUPLOAD-1772
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1772
 Project: maven-upload-requests
  Issue Type: New Feature
Reporter: Michael Nyika
 Attachments: maven-grester-plugin-1.0-bundle.jar

Grester is a Maven2 Plugin for Jester. Grester's groupId for version 1.0 has 
been changed to grester.sf.net (from the previous org.apache.maven.plugins 
which is reserved for apache.org ).

-- 
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: (MAVENUPLOAD-1763) Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110180
 ] 

Michael Nyika edited comment on MAVENUPLOAD-1763 at 10/17/07 9:52 AM:
--

I will change the groupId appropriately and then create a new issue with the 
corrected change bundle attached. Thanks Carlos.


 was:
The developer will change the groupId appropriately and then create a new issue 
with the corrected change bundle attached. Thanks Carlos.

 Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository
 -

 Key: MAVENUPLOAD-1763
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1763
 Project: maven-upload-requests
  Issue Type: New Feature
Reporter: Michael Nyika
 Attachments: maven-grester-plugin-0.3-bundle.jar


 The Grester 0.3 Bundle is a Maven Plugin for Unit Testing. It is used 
 together with Jester and JUnit to test source code. 

-- 
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: (MAVENUPLOAD-1763) Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110180
 ] 

Michael Nyika edited comment on MAVENUPLOAD-1763 at 10/17/07 9:52 AM:
--

The developer will change the groupId appropriately and then create a new issue 
with the corrected change bundle attached. Thanks Carlos.


 was:
The developer will change the groupId appropriately and then upload the change.

 Need Grester 0.3 Bundlel to be uploaded into Ibiblio Maven Repository
 -

 Key: MAVENUPLOAD-1763
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1763
 Project: maven-upload-requests
  Issue Type: New Feature
Reporter: Michael Nyika
 Attachments: maven-grester-plugin-0.3-bundle.jar


 The Grester 0.3 Bundle is a Maven Plugin for Unit Testing. It is used 
 together with Jester and JUnit to test source code. 

-- 
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: (MAVENUPLOAD-1748) JUnit Toolkit 0.6 Maven Plugin


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rupert Smith closed MAVENUPLOAD-1748.
-

Resolution: Fixed

Incomplete request, will resubmit.

 JUnit Toolkit 0.6 Maven Plugin
 --

 Key: MAVENUPLOAD-1748
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1748
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Rupert Smith

 Maven plugin for JUnit Toolkit 0.6, to generate test scripts, or to run tests 
 directly as part of the build.

-- 
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: (MAVENUPLOAD-1767) Upload junit toolkit maven plugin 0.6.1


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rupert Smith closed MAVENUPLOAD-1767.
-

Resolution: Fixed

Incomplete request, will resubmit.

 Upload junit toolkit maven plugin 0.6.1
 ---

 Key: MAVENUPLOAD-1767
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1767
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Rupert Smith

 JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour 
 analysis, and concurrency testing.

-- 
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: (MAVENUPLOAD-1768) Upload junit toolkit 0.6.1


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rupert Smith closed MAVENUPLOAD-1768.
-

Resolution: Fixed

Incomplete request, will resubmit.

 Upload junit toolkit 0.6.1
 --

 Key: MAVENUPLOAD-1768
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1768
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Rupert Smith

 JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour 
 analysis, and concurrency testing.

-- 
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: (MAVENUPLOAD-1747) Junit Toolkit version 0.6


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rupert Smith closed MAVENUPLOAD-1747.
-

Resolution: Fixed

Incomplete request, will resubmit.

 Junit Toolkit version 0.6
 -

 Key: MAVENUPLOAD-1747
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1747
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Rupert Smith

 JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour 
 analysis, and concurrency testing.

-- 
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: (MPMD-63) Maven2 PMD Plugin should try to use the maven-compiler-plugin source level information

2007-10-17 Thread Baptiste MATHUS (JIRA)

Maven2 PMD Plugin should try to use the maven-compiler-plugin source level 
information
--

 Key: MPMD-63
 URL: http://jira.codehaus.org/browse/MPMD-63
 Project: Maven 2.x PMD Plugin
  Issue Type: Improvement
  Components: CPD, PMD
 Environment: Windows XP, maven 2.0.7
Reporter: Baptiste MATHUS
Priority: Minor


This plugin should retrieve the source level information from the 
maven-compiler plugin. In fact, this is a pity we've got to specify source 
level at different places (also for checkstyle, ...).

More generally, this information should be retrievable and used by any plugin. 
MPMD could still offer a way to override the settings, but it should not crash 
while parsing Java5 code since the code level has already been specified...

-- 
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: (MAVENUPLOAD-1761) Please enable rsyncing of MySQL Connector/J

2007-10-17 Thread Mark Matthews (JIRA)

[
http://jira.codehaus.org/browse/MAVENUPLOAD-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110193
]

Mark Matthews commented on MAVENUPLOAD-1761:

Okay, I re-did the repository. I'm not sure when Apache re-syncs to remote
repositories, but please let me knw if it works for you now?

Please enable rsyncing of MySQL Connector/J

Key: MAVENUPLOAD-1761
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1761
Project: maven-upload-requests
Issue Type: Bug
Reporter: Mark Matthews

From the dev mailing list -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Matthews wrote:
Hi folks,

We've been handing you .jars for awhile, but I finally got our web team
to setup a rsync repository so that we can do this automagically.

I have been working with Henri Yandell, through MAVENUPLOAD-1552, but I
wanted to see if you had any tools that could maintain the repository
structure based on the .jar files (with embedded POMs) that we've been
sending you.

We don't use Maven to build our stuff, so I'm not really clued in on
what I have to do to get this all to work. I'm perfectly okay if you
tell me to RTFM, I just don't know where in the manual to look this
stuff up.

Thanks in advance!

-Mark
Hi!
Okay, so I figured out how to do this. We've now got an rsync-able view
of the repository that contains MySQL Connector/J ready for you to pull
from at rsync.mysql.com:/web/sites/live/maven/ via SSH as user maven
with your public key from http://www.ibiblio.org/maven/id_dsa.pub.
Is this enough to go on, or do you need a shell script as well?
Let me know if the layout works for you!
-Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHBrO9tvXNTca6JD8RAv8hAJ4xFmrEJrU+HfUKG708tboFc2LsxgCfWP+S
QpI6wIPdh8uUN6cqKOBj02c=
=laWO
-END PGP SIGNATURE-

[jira] Created: (MSITE-261) Local Parent POM not found if relativePath specifies a directory

2007-10-17 Thread Benjamin Bentmann (JIRA)

Local Parent POM not found if relativePath specifies a directory
--

 Key: MSITE-261
 URL: http://jira.codehaus.org/browse/MSITE-261
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
  Components: multi module
Affects Versions: 2.0-beta-5
 Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
Reporter: Benjamin Bentmann
Priority: Minor
 Attachments: site-parent-pom.patch

The Maven core allows to specify a directory for the relativePath element in 
a module POM to locate the parent POM, e.g.{code:xml}parent
...
relativePath../parent/relativePath
/parent{code}will properly find the parent POM in ../parent/pom.xml. 
However, the Site plugin does not follow this lookup strategy:{code}
[INFO] [site:site]
[INFO] Unable to load parent project from a relative path: Could not find the 
model file '[SNIP]\..\parent'. for project unknown
[INFO] Parent project loaded from repository.{code}
This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a 
different message but fails, too.

The attached patch fixes this although I wonder whether this functionality is 
not already included somewhere in the Maven core (where is belongs IMHO).


-- 
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-2025) POM is still not read using the right encoding


 [ 
http://jira.codehaus.org/browse/MNG-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Fox closed MNG-2025.
--

Resolution: Fixed

fixed

 POM is still not read using the right encoding
 --

 Key: MNG-2025
 URL: http://jira.codehaus.org/browse/MNG-2025
 Project: Maven 2
  Issue Type: Bug
  Components: POM::Encoding
Affects Versions: 2.0
Reporter: Stefan Hübner
Assignee: Jason van Zyl
Priority: Critical
 Fix For: 2.0.8

 Attachments: MNG-2025-maven-model-testcases.patch, 
 MNG-2025-maven-project-testcases.patch


 IIRC XML standard says that default encoding is UTF-8 for xml files
 That can be overriden with 
 ?xml version=1.0 encoding=ISO-8859-1?
 But files without header saved as UTF8 are not parsed in some systems (eg 
 windows, solaris), while files saved as other encoding (I believe it was 
 ansi) break under a Mac mini with yellowdog linux

-- 
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: (MAVENUPLOAD-1761) Please enable rsyncing of MySQL Connector/J

[
http://jira.codehaus.org/browse/MAVENUPLOAD-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carlos Sanchez closed MAVENUPLOAD-1761.
---

Assignee: Carlos Sanchez
Resolution: Fixed

I have removed the invalid jars, the sync should happen again in 4 hours

Please enable rsyncing of MySQL Connector/J

Key: MAVENUPLOAD-1761
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1761
Project: maven-upload-requests
Issue Type: Bug
Reporter: Mark Matthews
Assignee: Carlos Sanchez

From the dev mailing list -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Matthews wrote:
Hi folks,

We've been handing you .jars for awhile, but I finally got our web team
to setup a rsync repository so that we can do this automagically.

Thanks in advance!

[jira] Commented: (MCOMPILER-60) Maven Eclipse Compiler has Classpath Resoluri

2007-10-17 Thread Ben Speiser (JIRA)


[ 
http://jira.codehaus.org/browse/MCOMPILER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110203
 ] 

Ben Speiser commented on MCOMPILER-60:
--

See issue in Plexus, PLXCOMP-84.

 Maven Eclipse Compiler has Classpath Resoluri
 -

 Key: MCOMPILER-60
 URL: http://jira.codehaus.org/browse/MCOMPILER-60
 Project: Maven 2.x Compiler Plugin
  Issue Type: Bug
Affects Versions: 2.0.2
 Environment: Windows XP; JDK 1.4; Maven 2.0.7
Reporter: Ben Speiser
 Attachments: MavenEclipseCompilerBug.zip


 The Maven Eclipse Compiler fails to find classes in rt.jar such as 
 org.omg.CORBA.Any, even with rt.jar hardcoded as a system dependency.  
 Sample project attached.  When switching to the default (javac) compiler, it 
 works fine.

-- 
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: (MAVENUPLOAD-1772) Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered)


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110207
 ] 

Carlos Sanchez commented on MAVENUPLOAD-1772:
-

should be net.sf.grester

 Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered)
 

 Key: MAVENUPLOAD-1772
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1772
 Project: maven-upload-requests
  Issue Type: New Feature
Reporter: Michael Nyika
 Attachments: maven-grester-plugin-1.0-bundle.jar


 Grester is a Maven2 Plugin for Jester. Grester's groupId for version 1.0 has 
 been changed to grester.sf.net (from the previous org.apache.maven.plugins 
 which is reserved for apache.org ).

-- 
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: (MAVENUPLOAD-1726) OpenDS Directory Server


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110208
 ] 

Carlos Sanchez commented on MAVENUPLOAD-1726:
-

I'm getting a warning that pom.xml is a binary file, some strage chars
The jar in the bundle must be named artifactId-version.jar case sensitive

 OpenDS Directory Server
 ---

 Key: MAVENUPLOAD-1726
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1726
 Project: maven-upload-requests
  Issue Type: Improvement
Reporter: Jasper Blues
Assignee: Carlos Sanchez
 Attachments: openDS-1.0.0-build005-bundle.jar, 
 openDS-1.0.0-build005-bundle.jar


 OpenDS is an open source community project building a free and comprehensive 
 next generation directory service. OpenDS is designed to address large 
 deployments, to provide high performance, to be highly extensible, and to be 
 easy to deploy, manage and monitor.
 Team List: https://opends.dev.java.net/public/misc/bios.html

-- 
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: (MAVENUPLOAD-1771) sync script for aislib


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-1771.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 sync script for aislib
 --

 Key: MAVENUPLOAD-1771
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1771
 Project: maven-upload-requests
  Issue Type: Wish
Reporter: Tomasz Pik
Assignee: Carlos Sanchez

 Please, setup a sync process for aislib.sf.net set of projects.
 aislib is a set of OS tools and libraries created by AIS.PL (www.ais.pl)
 Here's a script:
 #!/bin/sh
 CONTACTS=Tomasz Pik [EMAIL PROTECTED]
 MODE=rsync_ssh
 [EMAIL PROTECTED]:/home/groups/a/ai/aislib/htdocs/repos/sync
 GROUP_DIR=net/sf/aislib/

-- 
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: (CONTINUUM-150) Continuum site needs screenshots

2007-10-17 Thread Tom Schneider (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110214
 ] 

Tom Schneider commented on CONTINUUM-150:
-

Looking at http://maven.apache.org/continuum/ there is 1 screenshot, do we need 
more?  It looks like it's the latest 1.1 version, so unless more screenshots 
are needed I think this issue is already fixed.

 Continuum site needs screenshots
 

 Key: CONTINUUM-150
 URL: http://jira.codehaus.org/browse/CONTINUUM-150
 Project: Continuum
  Issue Type: Improvement
  Components: Documentation
Reporter: Henri Yandell
Priority: Minor
 Fix For: 1.1


 The Continuum site needs to show screenshots to better sell Continuum to 
 interested parties.

-- 
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: (CONTINUUM-150) Continuum site needs screenshots

2007-10-17 Thread Olivier Lamy (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110215
 ] 

Olivier Lamy commented on CONTINUUM-150:


we are working on a new documentation have a look here 
http://people.apache.org/~olamy/staging-sites/continuum/
:-)


 Continuum site needs screenshots
 

 Key: CONTINUUM-150
 URL: http://jira.codehaus.org/browse/CONTINUUM-150
 Project: Continuum
  Issue Type: Improvement
  Components: Documentation
Reporter: Henri Yandell
Priority: Minor
 Fix For: 1.1


 The Continuum site needs to show screenshots to better sell Continuum to 
 interested parties.

-- 
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: (CONTINUUM-150) Continuum site needs screenshots

2007-10-17 Thread Henri Yandell (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110219
 ] 

Henri Yandell commented on CONTINUUM-150:
-

I think that screenshot is good, along with a prominent link to a demo site 
(ie: vmbuild.apache.org).

 Continuum site needs screenshots
 

 Key: CONTINUUM-150
 URL: http://jira.codehaus.org/browse/CONTINUUM-150
 Project: Continuum
  Issue Type: Improvement
  Components: Documentation
Reporter: Henri Yandell
Priority: Minor
 Fix For: 1.1


 The Continuum site needs to show screenshots to better sell Continuum to 
 interested parties.

-- 
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: (MSITE-262) site.xml not inherited if build run from parent

2007-10-17 Thread Cameron Jones (JIRA)

site.xml not inherited if build run from parent
---

 Key: MSITE-262
 URL: http://jira.codehaus.org/browse/MSITE-262
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones


I've seen that the site.xml is not being inherited in a module when the build 
is run from the parent - when run from the module itself the inheritance works 
correctly.

-- 
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: (MSITE-263) NullPointerException if build run from a module and no url defined in module or parent

2007-10-17 Thread Cameron Jones (JIRA)

NullPointerException if build run from a module and no url defined in module or 
parent
--

 Key: MSITE-263
 URL: http://jira.codehaus.org/browse/MSITE-263
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Priority: Trivial


i've found that you get a null pointer exception if there is no url defined 
on a module or on it's parent pom. If the build is run from the parent it works 
but gives a warning that urls will not be decorated. Adding the url back to 
the parent fixes the issue. Here's the stacktrace:

java.lang.NullPointerException
at 
org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83)
at 
org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43)
at 
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334)
at 
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255)
at 
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277)
at 
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192)
at 
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83)
at 
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:251)
at 
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:525)
at 
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:464)
at 
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:114)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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

[jira] Created: (MSITE-264) Property names with periods are not resolved

2007-10-17 Thread Cameron Jones (JIRA)

Property names with periods are not resolved


 Key: MSITE-264
 URL: http://jira.codehaus.org/browse/MSITE-264
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones


I've been trying to get property filtering to work over the site documents as 
specified in http://maven.apache.org/plugins/maven-site-plugin/usage.html by 
appending the '.vm' extension to the appropriate files. The problem is that the 
property filtering doesn't seem to work when the property names contain periods 
for breaking up the context words, for example:

The works:
${currentVersion}

This doesn't:
${current.version}

For some reason the default maven properties which are always available do work 
even if they have periods, for example this is resolved correctly:

${project.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

[jira] Commented: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.


[ 
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110231
 ] 

Brett Porter commented on MRM-523:
--

no to not critical, or no to the creation of ~/.m2/archiva (which I still 
see)?

Does the server fail to start, or do the appearance actions just not work (I 
couldn't get a failure other than to try and edit the logo)?

 Appearance Actions do not work when ${user.home} is invalid.
 

 Key: MRM-523
 URL: http://jira.codehaus.org/browse/MRM-523
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
 Fix For: 1.x


 The reliance on maven core components with regards to Appearance / Company 
 Info / Edit Pom actions, prevents server installations without a valid user 
 $HOME directory. ( such as /dev/null )
 We should migrate away from maven core components at our earliest opportunity.

-- 
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: (MRM-546) Duplicate repositories show up while editing.


[ 
http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110232
 ] 

Brett Porter commented on MRM-546:
--

Work on this is block by the review of comments on r583412

 Duplicate repositories show up while editing.
 -

 Key: MRM-546
 URL: http://jira.codehaus.org/browse/MRM-546
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Critical

 Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to 
 1.0-beta-2.
 Situation: When editing the repositories, the repositories get duplicated.
 This is likely due to the fact that the configuration upgrade technique 
 from repositories to managedRepositories and remoteRepositories is not 
 removing the repositories section properly..
 Several efforts in the code have been made to correct this, but with no 
 success. See revision 583903 in archiva/trunk for details.

-- 
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-2593) Maven 2 stumbels upon non ASCII characters in the value of a localRepository value in the $HOME/.m2/settings.xml


 [ 
http://jira.codehaus.org/browse/MNG-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MNG-2593.
--

 Assignee: Herve Boutemy
   Resolution: Fixed
Fix Version/s: (was: 2.0.x)
   2.0.8

fixed in MNG-2254

 Maven 2 stumbels upon non ASCII characters in the value of a 
 localRepository value in the $HOME/.m2/settings.xml
 --

 Key: MNG-2593
 URL: http://jira.codehaus.org/browse/MNG-2593
 Project: Maven 2
  Issue Type: Bug
  Components: Settings
Affects Versions: 2.0.4
 Environment: Windows XP
 Maven 2.0.4
Reporter: Bernhard Wellhöfer
Assignee: Herve Boutemy
Priority: Blocker
 Fix For: 2.0.8


 I use a German Windows XP and my home folder is C:\Dokumente und 
 Einstellungen\Wellhöfer.
 When my C:\Dokumente und Einstellungen\Wellhöfer\.m2\settings.xml settings 
 file contains the line
 localRepositoryC:\Dokumente und 
 Einstellungen\Wellhöfer\.m2/localRepository
 downloaded artifacts are not put under C:\Dokumente und 
 Einstellungen\Wellhöfer\.m2. Maven2 creates a folder C:\Dokumente und 
 Einstellungen\WellhÃfer\.m2 and puts the artifacts into this folder.
 When I remove the line 
 localRepositoryC:\Dokumente und 
 Einstellungen\Wellhöfer\.m2/localRepository
 from settings.xml the artifacts are put into the correct 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] Commented: (MECLIPSE-228) CLONE -eclipse:eclipse goal should handle includes and excludes of the maven-compiler-plugin

2007-10-17 Thread Damon Jacobsen (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110240
 ] 

Damon Jacobsen commented on MECLIPSE-228:
-

Is this what the eclipse integration 0.11 is using to update source folders? 
This issue is bothersome.

 CLONE -eclipse:eclipse goal should handle includes and excludes of the 
 maven-compiler-plugin
 

 Key: MECLIPSE-228
 URL: http://jira.codehaus.org/browse/MECLIPSE-228
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Diego Ballve
Assignee: fabrizio giustina
 Fix For: 2.5

 Attachments: includeExclude.patch


 The maven-compiler-plugin allows a configuration such as:
   plugin
 artifactIdmaven-compiler-plugin/artifactId
 configuration
   excludes
 exclude**/idl/*Factory.java/exclude
   /excludes
 /configuration
   /plugin
 the generated .classpath file currently does not mention the excluded part:
   classpathentry kind=src path=src/main/java/
   classpathentry kind=src path=target/generated-sources/idl/
 which should be:
   classpathentry excluding=**/idl/*Factory.java kind=src 
 path=src/main/java/
   classpathentry excluding=**/idl/*Factory.java kind=src 
 path=target/generated-sources/idl/

-- 
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: (MRM-546) Duplicate repositories show up while editing.


[ 
http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110239
 ] 

Brett Porter commented on MRM-546:
--

also, do you have any explicit reproduction steps, since I've never actually 
experienced this (even when I upgraded from an old config, which I tested after 
my changes)?

 Duplicate repositories show up while editing.
 -

 Key: MRM-546
 URL: http://jira.codehaus.org/browse/MRM-546
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Critical

 Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to 
 1.0-beta-2.
 Situation: When editing the repositories, the repositories get duplicated.
 This is likely due to the fact that the configuration upgrade technique 
 from repositories to managedRepositories and remoteRepositories is not 
 removing the repositories section properly..
 Several efforts in the code have been made to correct this, but with no 
 success. See revision 583903 in archiva/trunk for details.

-- 
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: (MRM-546) Duplicate repositories show up while editing.


 [ 
http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter updated MRM-546:
-

Fix Version/s: 1.0-beta-4

 Duplicate repositories show up while editing.
 -

 Key: MRM-546
 URL: http://jira.codehaus.org/browse/MRM-546
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Critical
 Fix For: 1.0-beta-4


 Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to 
 1.0-beta-2.
 Situation: When editing the repositories, the repositories get duplicated.
 This is likely due to the fact that the configuration upgrade technique 
 from repositories to managedRepositories and remoteRepositories is not 
 removing the repositories section properly..
 Several efforts in the code have been made to correct this, but with no 
 success. See revision 583903 in archiva/trunk for details.

-- 
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: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.

[
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110243
]

Joakim Erdfelt commented on MRM-523:

The creation of $HOME/.m2/archiva is a result of reliance on the maven core
components, and should be filed as a separate bug.

This wasn't filed as critical, just major.

If someone decides to enter the appearance screens, as they are now, that whole
process fails.
Once the appearance screens have been activated, then the logs fill up
ridiculously fast with the exceptions, all tracked down to the appearance /
logo logic attempting to resolve content, on every access to every screen in
the application.

This is a severe problem.
We must address it.
Maybe not for the next pre-1.0 release, but definitely before 1.0 final.

Appearance Actions do not work when ${user.home} is invalid.

Key: MRM-523
URL: http://jira.codehaus.org/browse/MRM-523
Project: Archiva
Issue Type: Bug
Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
Fix For: 1.x

The reliance on maven core components with regards to Appearance / Company
Info / Edit Pom actions, prevents server installations without a valid user
$HOME directory. ( such as /dev/null )
We should migrate away from maven core components at our earliest opportunity.

[jira] Commented: (MRM-546) Duplicate repositories show up while editing.


[ 
http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110242
 ] 

Brett Porter commented on MRM-546:
--

ok, so that'd be no :)

I'll see if I can reproduce it.

 Duplicate repositories show up while editing.
 -

 Key: MRM-546
 URL: http://jira.codehaus.org/browse/MRM-546
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Critical
 Fix For: 1.0-beta-4


 Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to 
 1.0-beta-2.
 Situation: When editing the repositories, the repositories get duplicated.
 This is likely due to the fact that the configuration upgrade technique 
 from repositories to managedRepositories and remoteRepositories is not 
 removing the repositories section properly..
 Several efforts in the code have been made to correct this, but with no 
 success. See revision 583903 in archiva/trunk for details.

-- 
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-2932) Encoding chaos

[
http://jira.codehaus.org/browse/MNG-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herve Boutemy closed MNG-2932.
--

Assignee: Herve Boutemy
Resolution: Fixed

POM reading is fixed in MNG-2254: everything should work fine now

Encoding chaos
--

Key: MNG-2932
URL: http://jira.codehaus.org/browse/MNG-2932
Project: Maven 2
Issue Type: Bug
Components: POM::Encoding
Affects Versions: 2.0.4, 2.0.5, 2.0.6
Environment: windows, linux
Reporter: Jörg Hohwiller
Assignee: Herve Boutemy
Fix For: 2.0.8

I have tried maven on a project where javadocs, xdocs, pom-comments are in a
native language with many NON-ASCII characters.
This seems to reveal that maven is not acting clean with different encodings.
For instance the xdocs are XML. And XML allows me to use different encodings
if properly declared in the xml header. However it only works if I encode the
XML as UTF-8. If I use ISO-8859-1 then the produced HTML contains UTF-8
characters from the nationalized site messages (resource bundles of maven
plugins) and maven dumps the ISO-8859-1 encoded characters into that and ends
up with mixed encodings in one HTML page.
Additionally the JAVA files also cause trouble when I use a different
encoding than UTF-8. I configured the encoding for javadoc plugin to
ISO-8859-1 and used Java files in that encoding. The resulting javadoc HTML
was written in ISO-8859-1 but the browser displayed it as UTF-8 and I had to
switch explicitly to ISO-8859-1 in firefox in order to have the special
characters displayed properly.
Further I encounter trouble when I use special characters in pom.xml files
that go onto the generated web-site. In the end I could NOT find a way to
have a site without problems - even when I encode everything as UTF-8.
Maybe there are too few developers involved from non english-speaking
countries that are used to think beyond US-ASCII ;)
Unfortunatly I can not tell where the problems come from - it may be XPP,
doxia, site-plugin or individual reports or all together.
You need to properly distinguish between input and output encoding and have
to be extremly careful with Stuff like byte[]
and never parse XML from strings.
Can you reproduce the problem or do you need dummy projects as test-cases?

[jira] Commented: (MNG-1563) how to write integration tests


[ 
http://jira.codehaus.org/browse/MNG-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110238
 ] 

Herve Boutemy commented on MNG-1563:


Brian wrote 
http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test

 how to write integration tests
 --

 Key: MNG-1563
 URL: http://jira.codehaus.org/browse/MNG-1563
 Project: Maven 2
  Issue Type: Improvement
  Components: Design, Patterns  Best Practices
Reporter: Matthew Pocock
 Fix For: Documentation Deficit


 There doesn't seem to be a guide about either testing or integration testing. 
 It would be nice to see two guides:
 plain vanilla junit tests:
   how to write a simple one that will run in m2
   how to write one that uses the test suite API
 integration testing:
   test building e.g. plugin that does code generation
   test resulting application e.g. command-line app or gui
   test deployment e.g. to a test web service container
 I have no idea what of this is currently implemented or even possible using 
 mvn, but then the documentation isn't giving my wishes any boundaries 
 either...

-- 
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: (MCHECKSTYLE-78) Suppression filter is ignored

2007-10-17 Thread Peter F. Peterson (JIRA)

Suppression filter is ignored
-

 Key: MCHECKSTYLE-78
 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-78
 Project: Maven 2.x Checkstyle Plugin
  Issue Type: Bug
Affects Versions: 2.1
 Environment: Redhat Enterprise Linux, maven 2.0.6
Reporter: Peter F. Peterson


Inside my pom I have 
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-checkstyle-plugin/artifactId
  configuration
!--
configLocationsns_checkstyle_config.xml/configLocation
--
!--
configLocationconfig/sun_checks.xml/configLocation
--

suppressionsLocation${basedir}/src/checkstyle/suppressions.xml/suppressionsLocation
headerLocationLICENSE.txt/headerLocation
xrefLocationxref/xrefLocation
  /configuration
/plugin

And checkstyle fails to find the suppression file which is in the specified 
location. Here is the abbreviated build messages

[DEBUG] resolveLocation(null, checkstyle-packages.xml)
[DEBUG] 
resolveLocation(/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml,
 checkstyle-suppressions.xml)
[DEBUG] Location is not a URL.
[DEBUG] Potential File: 
/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An error has occurred in Checkstyle report generation.

Embedded error: failed to load suppressions location: 
/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
Connection timed out
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred 
in Checkstyle report generation.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:903)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error has 
occurred in Checkstyle report generation.
at 
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 19 more
Caused by: org.apache.maven.reporting.MavenReportException: failed to load 
suppressions location: 
/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
at 
org.apache.maven.plugin.checkstyle.CheckstyleReport.getSuppressions(CheckstyleReport.java:990)
at 
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:680)
at 
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:484)
at 
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
at 
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73)
... 21 more
Caused by:

[jira] Commented: (MRM-546) Duplicate repositories show up while editing.

[
http://jira.codehaus.org/browse/MRM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110241
]

Joakim Erdfelt commented on MRM-546:

It comes up often enough, I've seen it, others have seen it.
It's a bug. I filed it.

Copy/Paste from IRC this morning ...

{noformat}
eskatos I have a strange problem
eskatos all my snapshot are duplicated when I edit one
eskatos all my repositories are duplicated when I edit one
eskatos [ forget the snapshot line ]
bawt Topic forget the snapshot line does not exist
eskatos I mean, in my repositories page, I have each repository repeated 3
times ATM
eskatos If I edit one, I'll get every repository repeated 4 times right after
wsmoak eskatos: what version?
eskatos 1.0-beta2
wsmoak a workaround is to just edit archiva.xml and don't use the web ui
wsmoak I'm building the latest to check it, though joakim may be faster...
joakim eskatos, that's a but that i've been trying to get brett to fix. :-)
joakim eskatos, do this for a workaround. go into your $HOME/.m2/archiva.xml
and remove the repositories element and all content under it.
joakim s/that's a but/that's a bug/
eskatos not a butt either
eskatos ok thanks, I'll try this
wsmoak is it in JIRA? doesn't sound familiar.
joakim Can't find it.
wsmoak eskatos: can you (search and) open an issue for that problem?
joakim I'm opening it.
eskatos nice
wsmoak not something I've seen it do myself. but not surprising given the
other things it's done. :)
eskatos I won't try the workaround now, don't have much time today
joakim MRM-546
{noformat}

Duplicate repositories show up while editing.
-

Key: MRM-546
URL: http://jira.codehaus.org/browse/MRM-546
Project: Archiva
Issue Type: Bug
Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Critical

Environment: Using a pre 1.0-beta-2 archiva install that has been upgraded to
1.0-beta-2.
Situation: When editing the repositories, the repositories get duplicated.
This is likely due to the fact that the configuration upgrade technique
from repositories to managedRepositories and remoteRepositories is not
removing the repositories section properly..
Several efforts in the code have been made to correct this, but with no
success. See revision 583903 in archiva/trunk for details.

[jira] Commented: (MRM-523) Appearance Actions do not work when ${user.home} is invalid.


[ 
http://jira.codehaus.org/browse/MRM-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110244
 ] 

Brett Porter commented on MRM-523:
--

suggested workaround to avoid the log spam: set -Duser.home in the wrapper (or 
HOME in the env) before running to an effectively-homeless but writeable 
location (eg /tmp/archiva-home) - the account can still have no real home, this 
is just to tell Java where to treat $HOME.

Will fix this properly in 1.x - I would suggest:
- sourcing from the managed repositories instead of remote
- proxying if necessary
- not needing a local repository
- when saving a new POM, allow selection of the managed repository to store to

This makes the actions more specific to Archiva, so might need to come up with 
something easier to work with there so we don't diverge from what is used in 
Continuum.

 Appearance Actions do not work when ${user.home} is invalid.
 

 Key: MRM-523
 URL: http://jira.codehaus.org/browse/MRM-523
 Project: Archiva
  Issue Type: Bug
  Components: system
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Brett Porter
Priority: Minor
 Fix For: 1.x


 The reliance on maven core components with regards to Appearance / Company 
 Info / Edit Pom actions, prevents server installations without a valid user 
 $HOME directory. ( such as /dev/null )
 We should migrate away from maven core components at our earliest opportunity.

-- 
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: (MAVENUPLOAD-1726) OpenDS Directory Server

2007-10-17 Thread Jasper Blues (JIRA)


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110245
 ] 

Jasper Blues commented on MAVENUPLOAD-1726:
---

Stupid windows - I tried doing this on site on a training box. I'll fix it up 
tomorrow when I get back home (can't find a port for my laptop). Hold on!

 OpenDS Directory Server
 ---

 Key: MAVENUPLOAD-1726
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1726
 Project: maven-upload-requests
  Issue Type: Improvement
Reporter: Jasper Blues
Assignee: Carlos Sanchez
 Attachments: openDS-1.0.0-build005-bundle.jar, 
 openDS-1.0.0-build005-bundle.jar


 OpenDS is an open source community project building a free and comprehensive 
 next generation directory service. OpenDS is designed to address large 
 deployments, to provide high performance, to be highly extensible, and to be 
 easy to deploy, manage and monitor.
 Team List: https://opends.dev.java.net/public/misc/bios.html

-- 
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] Moved: (MNG-3244) inherited site url not properly handling parameters


 [ 
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez moved MSITE-144 to MNG-3244:
---

Affects Version/s: (was: 2.0-beta-5)
  Component/s: (was: inheritance)
   Sites  Reporting
   Inheritance and Interpolation
  Key: MNG-3244  (was: MSITE-144)
  Project: Maven 2  (was: Maven 2.x Site Plugin)

 inherited site url not properly handling parameters
 ---

 Key: MNG-3244
 URL: http://jira.codehaus.org/browse/MNG-3244
 Project: Maven 2
  Issue Type: Bug
  Components: Inheritance and Interpolation, Sites  Reporting
Reporter: Jacob Robertson

 Here is the test case to reroduce this problem.  Take the following two 
 pom.xml files
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdfoo/artifactId
   namefoo/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   distributionManagement
   site
   idfoo-site/id
   urlfile://C:/Documents and 
 Settings/foo/.m2/site/${project.artifactId}/url
   /site
   /distributionManagement
 /project
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdbaz/artifactId
   namebaz/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   parent
   artifactIdfoo/artifactId
   groupIdorg.bar/groupId
   version1.0-SNAPSHOT/version
   /parent
 /project
 And run the site-deploy goal on each.  What you get under the site directory 
 is this
 - site
 /- foo
 ---/site docs
 /- baz
 ---/- baz (extra directory)
 --- ---/site docs
 This is the simplest test case.  In the case where I have a grandparent 
 pom, the site directory uses the grandparent/parent as the path to the site, 
 and doesn't use the actual artifactId of the artifact I'm creating the site 
 for.

-- 
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-3244) inherited site url not properly handling parameters

2007-10-17 Thread James William Dumay (JIRA)


 [ 
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James William Dumay updated MNG-3244:
-

Attachment: fix-inherited-site-url.patch

Here is a fix for Maven 2.0.8 with tests.

 inherited site url not properly handling parameters
 ---

 Key: MNG-3244
 URL: http://jira.codehaus.org/browse/MNG-3244
 Project: Maven 2
  Issue Type: Bug
  Components: Inheritance and Interpolation, Sites  Reporting
Reporter: Jacob Robertson
 Attachments: fix-inherited-site-url.patch


 Here is the test case to reroduce this problem.  Take the following two 
 pom.xml files
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdfoo/artifactId
   namefoo/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   distributionManagement
   site
   idfoo-site/id
   urlfile://C:/Documents and 
 Settings/foo/.m2/site/${project.artifactId}/url
   /site
   /distributionManagement
 /project
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdbaz/artifactId
   namebaz/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   parent
   artifactIdfoo/artifactId
   groupIdorg.bar/groupId
   version1.0-SNAPSHOT/version
   /parent
 /project
 And run the site-deploy goal on each.  What you get under the site directory 
 is this
 - site
 /- foo
 ---/site docs
 /- baz
 ---/- baz (extra directory)
 --- ---/site docs
 This is the simplest test case.  In the case where I have a grandparent 
 pom, the site directory uses the grandparent/parent as the path to the site, 
 and doesn't use the actual artifactId of the artifact I'm creating the site 
 for.

-- 
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-3244) inherited site url not properly handling parameters


 [ 
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Fox updated MNG-3244:
---

 Assignee: Brian Fox
Affects Version/s: 2.0.7
Fix Version/s: 2.0.8

 inherited site url not properly handling parameters
 ---

 Key: MNG-3244
 URL: http://jira.codehaus.org/browse/MNG-3244
 Project: Maven 2
  Issue Type: Bug
  Components: Inheritance and Interpolation, Sites  Reporting
Affects Versions: 2.0.7
Reporter: Jacob Robertson
Assignee: Brian Fox
 Fix For: 2.0.8

 Attachments: fix-inherited-site-url.patch


 Here is the test case to reroduce this problem.  Take the following two 
 pom.xml files
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdfoo/artifactId
   namefoo/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   distributionManagement
   site
   idfoo-site/id
   urlfile://C:/Documents and 
 Settings/foo/.m2/site/${project.artifactId}/url
   /site
   /distributionManagement
 /project
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdbaz/artifactId
   namebaz/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   parent
   artifactIdfoo/artifactId
   groupIdorg.bar/groupId
   version1.0-SNAPSHOT/version
   /parent
 /project
 And run the site-deploy goal on each.  What you get under the site directory 
 is this
 - site
 /- foo
 ---/site docs
 /- baz
 ---/- baz (extra directory)
 --- ---/site docs
 This is the simplest test case.  In the case where I have a grandparent 
 pom, the site directory uses the grandparent/parent as the path to the site, 
 and doesn't use the actual artifactId of the artifact I'm creating the site 
 for.

-- 
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-3244) inherited site url not properly handling parameters


 [ 
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Fox closed MNG-3244.
--

Resolution: Fixed

Thanks for the patch. I updated it to handle \ in the path and another small 
issue I found while testing.

 inherited site url not properly handling parameters
 ---

 Key: MNG-3244
 URL: http://jira.codehaus.org/browse/MNG-3244
 Project: Maven 2
  Issue Type: Bug
  Components: Inheritance and Interpolation, Sites  Reporting
Affects Versions: 2.0.7
Reporter: Jacob Robertson
Assignee: Brian Fox
 Fix For: 2.0.8

 Attachments: fix-inherited-site-url.patch


 Here is the test case to reroduce this problem.  Take the following two 
 pom.xml files
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdfoo/artifactId
   namefoo/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   distributionManagement
   site
   idfoo-site/id
   urlfile://C:/Documents and 
 Settings/foo/.m2/site/${project.artifactId}/url
   /site
   /distributionManagement
 /project
 ?xml version=1.0 encoding=UTF-8?
 project
   groupIdorg.bar/groupId
   artifactIdbaz/artifactId
   namebaz/name
   version1.0-SNAPSHOT/version
   packagingpom/packaging
   modelVersion4.0.0/modelVersion
   parent
   artifactIdfoo/artifactId
   groupIdorg.bar/groupId
   version1.0-SNAPSHOT/version
   /parent
 /project
 And run the site-deploy goal on each.  What you get under the site directory 
 is this
 - site
 /- foo
 ---/site docs
 /- baz
 ---/- baz (extra directory)
 --- ---/site docs
 This is the simplest test case.  In the case where I have a grandparent 
 pom, the site directory uses the grandparent/parent as the path to the site, 
 and doesn't use the actual artifactId of the artifact I'm creating the site 
 for.

-- 
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-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range


[ 
http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110254
 ] 

Brian Fox commented on MNG-2123:


Any one of the voters/watchers care to make an IT for this? 
http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test

 NullPointerException when a dependency uses version range and another uses an 
 actual version incompatible with that range
 -

 Key: MNG-2123
 URL: http://jira.codehaus.org/browse/MNG-2123
 Project: Maven 2
  Issue Type: Bug
  Components: Dependencies
Affects Versions: 2.0.2, 2.0.3, 2.0.4
Reporter: Carlos Sanchez
Assignee: Jason van Zyl
 Fix For: 2.0.8

 Attachments: MNG-2123-maven-artifact.patch, pom.xml

   Original Estimate: 4 hours
  Remaining Estimate: 4 hours

 Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,)
 Build fails with a null pointer exception that is not very explanatory
 [INFO] Scanning for projects...
 [INFO] 
 
 [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT
 [INFO]task-segment: [test]
 [INFO] 
 
 [INFO] [resources:resources]
 [INFO] Using default encoding to copy filtered resources.
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] version was null for commons-digester:commons-digester
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException: version was null for 
 commons-digester:commons-digester
 at 
 org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361)
 at 
 org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222)
 at 
 org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182)
 at 
 org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
 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)
 [INFO] 
 
 [INFO] Total time: 1 second
 [INFO] Finished at: Sun Mar 05 23:26:16 PST 2006
 [INFO] Final Memory: 3M/5M
 [INFO] 
 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the

[jira] Commented: (MNG-2339) ${project.*} are interpreted in the wrong place


[ 
http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110255
 ] 

Brian Fox commented on MNG-2339:


Any one of the watchers/ voters care to make an IT test for this? 
http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test

 ${project.*} are interpreted in the wrong place
 ---

 Key: MNG-2339
 URL: http://jira.codehaus.org/browse/MNG-2339
 Project: Maven 2
  Issue Type: Bug
  Components: General
Affects Versions: 2.0.4
Reporter: Emmanuel Venisse
Assignee: Kenney Westerhof
Priority: Critical
 Fix For: 2.0.8


 If a plugin use ${project.version}, this parameter is interpreted with the 
 version of the current project and not the plugin version. I think we have 
 the same pb with dependencies and other ${project.*}
 For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT, 
 ${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT 
 instead of 2.0

-- 
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-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987

2007-10-17 Thread James William Dumay (JIRA)

Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
---

 Key: MNG-3245
 URL: http://jira.codehaus.org/browse/MNG-3245
 Project: Maven 2
  Issue Type: Bug
  Components: Sites  Reporting
Affects Versions: 2.0.8
Reporter: James William Dumay
Priority: Blocker
 Attachments: sample-exception-report.txt

See example exception file attached.

I tracked the problem down to this change:

r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines
o bumped to the release doxia-sink-api
o used org.apache.maven.doxia.sink.Sink instead of the deprecated 
org.codehaus.doxia.sink.Sink

Ill attempt a rollback locally of the change and report 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

[jira] Updated: (MNG-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987