[jira] (DOXIA-513) Add support for {color}
Borut Bolcina created DOXIA-513:
---
Summary: Add support for {color}
Key: DOXIA-513
URL: https://jira.codehaus.org/browse/DOXIA-513
Project: Maven Doxia
Issue Type: Improvement
Reporter: Borut Bolcina
Basic color support would be really nice.
{color:green}some green text{color}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"
Deploying site with sftp or scp creates directory with name "-p" Key: MSITE-145 URL: http://jira.codehaus.org/browse/MSITE-145 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-5 Environment: Windows XP SP2, maven 2.0.4 Reporter: Borut Bolcina On Windows XP, with maven 2.0.4 and site plugin 2.0-beta-5 when doing site:deploy with website my project site sftp://my.server/project a command mkdir -p /project/ is issued which I think is not correct When executing from cmd window C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>ftp my.server Connected to my.server. 220 (vsFTPd 2.0.3) User (my.server:(none)): myusername 331 Please specify the password. Password: 230 Login successful. ftp> mkdir -p /project/ 257 "/-p" created ftp> Instead of creating /project directory, the ftp client creates a directory with name "-p". I think that is the reason the site:deploy fails. See bellow. C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn site:deploy [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] [INFO] Building MyProject [INFO]task-segment: [site:deploy] [INFO] [INFO] [site:deploy] The authenticity of host 'my.server' can't be established. RSA key fingerprint is 4a:86:2b:a7:15:29:ee:4b:10:8f:8e:73:53:b0:9e:cd. Are you sure you want to continue connecting? (yes/no): yes sftp://my.server/project - Session: Opened Executing command: mkdir -p /project/. sftp://my.server/project - Session: Disconnecting sftp://my.server/project - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Error performing commands for file transfer Exit code: 1 - mkdir: cannot create directory `/project': Permission denied [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Thu Jun 01 23:06:05 CEST 2006 [INFO] Final Memory: 7M/13M [INFO] The same happens when trying to deploy with scp. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"
[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66451 ] Borut Bolcina commented on MSITE-145: - This is not true! I can make make directories just fine. Please read the issue carefully. The directory with name of the first parameter gets created which is "-p" in the above case. Also I can create files and dirs with my other ftp (visual) client tools, so the permission should not be the case. Regards, Borut P.S. What do you mean ftp in NOT ftp? > Deploying site with sftp or scp creates directory with name "-p" > > > Key: MSITE-145 > URL: http://jira.codehaus.org/browse/MSITE-145 > Project: Maven 2.x Site Plugin > Type: Bug > Versions: 2.0-beta-5 > Environment: Windows XP SP2, maven 2.0.4 > Reporter: Borut Bolcina > Assignee: Carlos Sanchez > > > On Windows XP, with maven 2.0.4 and site plugin 2.0-beta-5 when doing > site:deploy with > > >website >my project site >sftp://my.server/project > > > a command mkdir -p /project/ is issued which I think is not correct > When executing from cmd window >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>ftp >my.server >Connected to my.server. >220 (vsFTPd 2.0.3) >User (my.server:(none)): myusername >331 Please specify the password. >Password: >230 Login successful. >ftp> mkdir -p /project/ >257 "/-p" created >ftp> > Instead of creating /project directory, the ftp client creates a directory > with name "-p". I think that is the reason the site:deploy fails. See bellow. >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn >site:deploy >[INFO] Scanning for projects... >[INFO] Searching repository for plugin with prefix: 'site'. >[INFO] > > >[INFO] Building MyProject >[INFO]task-segment: [site:deploy] >[INFO] > > >[INFO] [site:deploy] >The authenticity of host 'my.server' can't be established. >RSA key fingerprint is 4a:86:2b:a7:15:29:ee:4b:10:8f:8e:73:53:b0:9e:cd. >Are you sure you want to continue connecting? (yes/no): yes >sftp://my.server/project - Session: Opened >Executing command: mkdir -p /project/. >sftp://my.server/project - Session: Disconnecting >sftp://my.server/project - Session: Disconnected >[INFO] > >[ERROR] BUILD ERROR >[INFO] > >[INFO] Error uploading site >Embedded error: Error performing commands for file transfer >Exit code: 1 - mkdir: cannot create directory `/project': Permission >denied >[INFO] > >[INFO] For more information, run Maven with the -e switch >[INFO] > >[INFO] Total time: 10 seconds >[INFO] Finished at: Thu Jun 01 23:06:05 CEST 2006 >[INFO] Final Memory: 7M/13M >[INFO] > > The same happens when trying to deploy with scp. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"
[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66534 ] Borut Bolcina commented on MSITE-145: - With ftp and added org.apache.maven.wagon wagon-ftp under , I get C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn site:deploy [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] artifact org.apache.maven.wagon:wagon-ftp: checking for updates from agilejava [INFO] artifact org.apache.maven.wagon:wagon-ftp: checking for updates from central Downloading: http://mirrors.dotsrc.org/maven2/org/apache/maven/wagon/wagon-ftp/1.0-alpha-6/wagon-ftp-1.0-alpha -6.pom 806b downloaded Downloading: http://agilejava.com/maven/org/apache/maven/wagon/wagon-providers/1.0-alpha-6/wagon-providers-1.0 -alpha-6.pom [WARNING] Unable to get resource from repository agilejava (http://agilejava.com/maven) Downloading: http://mirrors.dotsrc.org/maven2/org/apache/maven/wagon/wagon-providers/1.0-alpha-6/wagon-provide rs-1.0-alpha-6.pom 1K downloaded Downloading: http://agilejava.com/maven/commons-net/commons-net/1.4.1/commons-net-1.4.1.pom [WARNING] Unable to get resource from repository agilejava (http://agilejava.com/maven) Downloading: http://mirrors.dotsrc.org/maven2/commons-net/commons-net/1.4.1/commons-net-1.4.1.pom 4K downloaded Downloading: http://mirrors.dotsrc.org/maven2/org/apache/maven/wagon/wagon-ftp/1.0-alpha-6/wagon-ftp-1.0-alpha -6.jar 8K downloaded Downloading: http://agilejava.com/maven/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar [WARNING] Unable to get resource from repository agilejava (http://agilejava.com/maven) Downloading: http://mirrors.dotsrc.org/maven2/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar 176K downloaded [INFO] [INFO] Building MyProject [INFO]task-segment: [site:deploy] [INFO] [INFO] [site:deploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Wagon protocol 'ftp' doesn't support directory copying [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Sat Jun 03 12:18:53 CEST 2006 [INFO] Final Memory: 7M/15M [INFO] which is http://jira.codehaus.org/browse/WAGONFTP-7 I guess I am stuck. > Deploying site with sftp or scp creates directory with name "-p" > > > Key: MSITE-145 > URL: http://jira.codehaus.org/browse/MSITE-145 > Project: Maven 2.x Site Plugin > Type: Bug > Versions: 2.0-beta-5 > Environment: Windows XP SP2, maven 2.0.4 > Reporter: Borut Bolcina > Assignee: Carlos Sanchez > > > On Windows XP, with maven 2.0.4 and site plugin 2.0-beta-5 when doing > site:deploy with > > >website >my project site >sftp://my.server/project > > > a command mkdir -p /project/ is issued which I think is not correct > When executing from cmd window >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>ftp >my.server >Connected to my.server. >220 (vsFTPd 2.0.3) >User (my.server:(none)): myusername >331 Please specify the password. >Password: >230 Login successful. >ftp> mkdir -p /project/ >257 "/-p" created >ftp> > Instead of creating /project directory, the ftp client creates a directory > with name "-p". I think that is the reason the site:deploy fails. See bellow. >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn >site:deploy >[INFO] Scanning for projects... >[INFO] Searching repository for plugin with prefix: 'site'. >[INFO] > > >[INFO] Building MyProject >[INFO]task-segment: [site:deploy] >[INFO] > > >[INFO] [site:deploy] >The authenticity of host 'my.server' can't be established. >RSA key fingerprint is 4a:86:2b:a7:15:29:ee:4b:10:8f:8e:73:53:b0:9e:cd. >Are you sure you want to continue connecting? (yes/no): yes >sftp://my.server/project - Session: Opened >Executing command: mkdir -p /project/. >sftp://my.server/project - Session: Disconnecting >sftp://my.server/project - Session: Disconnected >[INFO] > >[ERROR] BUILD ERROR >[INFO] >--
[jira] Commented: (MSITE-145) Deploying site with sftp or scp creates directory with name "-p"
[ http://jira.codehaus.org/browse/MSITE-145?page=comments#action_66575 ] Borut Bolcina commented on MSITE-145: - I managed to deploy my site with scp. > Deploying site with sftp or scp creates directory with name "-p" > > > Key: MSITE-145 > URL: http://jira.codehaus.org/browse/MSITE-145 > Project: Maven 2.x Site Plugin > Type: Bug > Versions: 2.0-beta-5 > Environment: Windows XP SP2, maven 2.0.4 > Reporter: Borut Bolcina > Assignee: Carlos Sanchez > > > On Windows XP, with maven 2.0.4 and site plugin 2.0-beta-5 when doing > site:deploy with > > >website >my project site >sftp://my.server/project > > > a command mkdir -p /project/ is issued which I think is not correct > When executing from cmd window >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>ftp >my.server >Connected to my.server. >220 (vsFTPd 2.0.3) >User (my.server:(none)): myusername >331 Please specify the password. >Password: >230 Login successful. >ftp> mkdir -p /project/ >257 "/-p" created >ftp> > Instead of creating /project directory, the ftp client creates a directory > with name "-p". I think that is the reason the site:deploy fails. See bellow. >C:\Documents and Settings\Borut\Desktop\Workspace\MyProject>mvn >site:deploy >[INFO] Scanning for projects... >[INFO] Searching repository for plugin with prefix: 'site'. >[INFO] > > >[INFO] Building MyProject >[INFO]task-segment: [site:deploy] >[INFO] > > >[INFO] [site:deploy] >The authenticity of host 'my.server' can't be established. >RSA key fingerprint is 4a:86:2b:a7:15:29:ee:4b:10:8f:8e:73:53:b0:9e:cd. >Are you sure you want to continue connecting? (yes/no): yes >sftp://my.server/project - Session: Opened >Executing command: mkdir -p /project/. >sftp://my.server/project - Session: Disconnecting >sftp://my.server/project - Session: Disconnected >[INFO] > >[ERROR] BUILD ERROR >[INFO] > >[INFO] Error uploading site >Embedded error: Error performing commands for file transfer >Exit code: 1 - mkdir: cannot create directory `/project': Permission >denied >[INFO] > >[INFO] For more information, run Maven with the -e switch >[INFO] > >[INFO] Total time: 10 seconds >[INFO] Finished at: Thu Jun 01 23:06:05 CEST 2006 >[INFO] Final Memory: 7M/13M >[INFO] > > The same happens when trying to deploy with scp. -- 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: (WAGON-57) Error deploying 3rd party jar to company webdav repository
Error deploying 3rd party jar to company webdav repository -- Key: WAGON-57 URL: http://jira.codehaus.org/browse/WAGON-57 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-1 Environment: win xp, jdk 1.5.0_06-b05, maven 2.0.4 Reporter: Borut Bolcina Attachments: output.txt Deploying activation jar to company webdav repository fails mvn -X deploy:deploy-file -DgroupId=javax.activation -DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar -Dfile=activation.jar -DrepositoryId=interseek-maven-repository -Durl=dav:https://maven.noviforum.si Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav See atached file for complete console output of the error. I suspect version conflicts. My coworker on linux succeded at deploying some other sun jar on the same company repo. The documentation says: First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your %M2_HOME%/lib. I copied wagon-webdav-1.0-beta-1.jar there, but it doesn't help. -- 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: (WAGON-57) Error deploying 3rd party jar to company webdav repository
[ http://jira.codehaus.org/browse/WAGON-57?page=comments#action_70800 ] Borut Bolcina commented on WAGON-57: I copied jakarta-slide-webdavlib-2.1.jar commons-httpclient-3.0.jar Now I am getting [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav (class: org/apache/maven/wagon/providers/webdav/WebDavWagon, method: openConnection signature: ()V) Incompatible object argument f or function call > Error deploying 3rd party jar to company webdav repository > -- > > Key: WAGON-57 > URL: http://jira.codehaus.org/browse/WAGON-57 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-1 > Environment: win xp, jdk 1.5.0_06-b05, maven 2.0.4 >Reporter: Borut Bolcina > Assigned To: Carlos Sanchez > Attachments: output.txt > > > Deploying activation jar to company webdav repository fails > mvn -X deploy:deploy-file -DgroupId=javax.activation -DartifactId=activation > -Dversion=1.0.2 -Dpackaging=jar -Dfile=activation.jar > -DrepositoryId=interseek-maven-repository -Durl=dav:https://maven.noviforum.si > Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon > which supports the requested protocol: dav > See atached file for complete console output of the error. > I suspect version conflicts. My coworker on linux succeded at deploying some > other sun jar on the same company repo. The documentation says: > First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to > your %M2_HOME%/lib. > I copied wagon-webdav-1.0-beta-1.jar there, but it doesn't help. -- 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: (WAGON-57) Error deploying 3rd party jar to company webdav repository
[ http://jira.codehaus.org/browse/WAGON-57?page=comments#action_70808 ] Borut Bolcina commented on WAGON-57: Thanks for your input Carlos. I added one more jar (commons-logging) and it works now. During upload I got lots of this messages (INFO: Redirect requested but followRedirects is disabled) Uploading: https://maven.noviforum.si/javax/activation/activation/1.0.2/activation-1.0.2.jar 26.7.2006 22:09:49 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled 26.7.2006 22:09:49 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled 26.7.2006 22:09:49 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled 26.7.2006 22:09:49 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled 26.7.2006 22:09:49 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse .. Is there some setting to enable redirects? Anyway, the upload works - activation jar and accompanied files are all there in internal repo. > Error deploying 3rd party jar to company webdav repository > -- > > Key: WAGON-57 > URL: http://jira.codehaus.org/browse/WAGON-57 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-1 > Environment: win xp, jdk 1.5.0_06-b05, maven 2.0.4 >Reporter: Borut Bolcina > Assigned To: Carlos Sanchez > Attachments: output.txt > > > Deploying activation jar to company webdav repository fails > mvn -X deploy:deploy-file -DgroupId=javax.activation -DartifactId=activation > -Dversion=1.0.2 -Dpackaging=jar -Dfile=activation.jar > -DrepositoryId=interseek-maven-repository -Durl=dav:https://maven.noviforum.si > Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon > which supports the requested protocol: dav > See atached file for complete console output of the error. > I suspect version conflicts. My coworker on linux succeded at deploying some > other sun jar on the same company repo. The documentation says: > First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to > your %M2_HOME%/lib. > I copied wagon-webdav-1.0-beta-1.jar there, but it doesn't help. -- 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-3752) Preparing release fails with svn client 1.5.1 and 1.5.2
Preparing release fails with svn client 1.5.1 and 1.5.2
---
Key: MNG-3752
URL: http://jira.codehaus.org/browse/MNG-3752
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Maven version: 2.0.9
Java version: 1.5.0_11
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Subversion command-line client, version 1.5.2
Reporter: Borut Bolcina
Priority: Blocker
When upgraded svn client from 1.5.0-dev to 1.5.2 the _mvn release:prepare_
fails:
{code}[INFO] Executing: svn --non-interactive commit --file
C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-2091962435.commit --targets
C:\DOCUME~1\borutb\L
OCALS~1\Temp\maven-scm-44156-targets
[INFO] Working directory: C:\workarea\madserver-RB-1.3
[INFO] Tagging release with the label REL-1.3.10...
[INFO] Executing: svn --non-interactive copy --file
C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-855569361.commit .
https://svn.acme.com/repos
itories/modules/madserver/tags/REL-1.3.10
[INFO] Working directory: C:\workarea\madserver-RB-1.3
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File
'/repositories/modules/madserver/tags/REL-1.3.10/.settings/org.maven.ide.eclipse.prefs'
already exists
{code}
The same happens with 1.5.1 svn client on Linux with my coworker. Installing
1.5.0 solves the problem. As temporary files (.commit) are deleted I can not
give more 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] Created: (MNG-3784) Failed to validate POM for project ... at ...\release-pom.xml
Failed to validate POM for project ... at ...\release-pom.xml
-
Key: MNG-3784
URL: http://jira.codehaus.org/browse/MNG-3784
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Reporter: Borut Bolcina
When releasing the multimodule project and one of the transitive dependencies
is tools.jar a fatal error occurs.
mvn release:prepare -DgenerateReleasePoms=true
...
[INFO] Executing: mvn clean verify --no-plugin-updates -P proxy
[INFO] Scanning for projects...
[INFO] NOTE: Using release-pom:
C:\eclipse\workspace\trident-project\release-pom.xml in reactor build.
[INFO] NOTE: Using release-pom:
C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml in reactor
build.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: com.interseek:trident-admin
POM Location:
C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
Validation Messages:
[0] For dependency Dependency {groupId=com.sun, artifactId=tools,
version=1.5.0, type=jar}: system-scoped dependency must specify systemPath.
Reason: Failed to validate POM for project com.interseek:trident-admin
at C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate
POM for project com.interseek:trident-admin at
C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException:
Failed to validate POM for project com.interseek:trident-admin at
C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
... 11 more
[INFO]
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Oct 08 11:14:22 CEST 2008
[INFO] Final Memory: 1M/2M
[INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Maven execution failed, exit code: '1'
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 57 seconds
[INFO] Finished at: Wed Oct 08 11:14:22 CEST 2008
[INFO] Final Memory: 8M/14M
[INFO]
The 3rd party pom has this in the POM:
defa
[jira] Commented: (MNG-3685) Dependency can't be resolved but has been found in the reactor.
[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150291#action_150291 ] Borut Bolcina commented on MNG-3685: We are having this issue too. When doing mvn release:prepare and the artifact was not installed previously, it complains with "...SNAPSHOT can't be resolved but has been found in the reactor.". We use Maven 2.0.9. > Dependency can't be resolved but has been found in the reactor. > --- > > Key: MNG-3685 > URL: http://jira.codehaus.org/browse/MNG-3685 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Jörg Hohwiller > Fix For: 2.0.11 > > > Since I upgraded maven to 2.0.9, I get messages like the following endlessly: > Downloading: > http://m-m-m.sourceforge.net/repository/net/sf/m-m-m/mmm-util-core/1.0.2-SNAPSHOT/mmm-util-core-1.0.2-SNAPSHOT.jar > [WARNING] The dependency: net.sf.m-m-m:mmm-util-core:jar:1.0.2-SNAPSHOT can't > be resolved but has been found in the reactor. > This dependency has been excluded from the plugin execution. You should rerun > this mojo after executing mvn install. > This also happens, if someone checks out the project and does "mvn > eclipse:eclipse". The process still works but takes extraordinary long to > proceed because it scales about n^2 with n beiing the number of modules in > your reactor. > You should also take into account that "mvn install" aborts if some tests > fail. > Sorry to say so, but this behaviour of maven is absolutely inacceptable. I > hope there is a chance to fix this in the next release(s). Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-218) Ignoring links element in the configuration
Ignoring links element in the configuration
---
Key: MJAVADOC-218
URL: http://jira.codehaus.org/browse/MJAVADOC-218
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Reporter: Borut Bolcina
The links elements are ignored - here is the plugin configuration:
maven-javadoc-plugin
ydoc.doclets.YStandard
C:/ydoc-3.0_01-jdk1.5/lib/ydoc.jar;C:/ydoc-3.0_01-jdk1.5/resources;${build.classes.dir}
-umlautogen
http://java.sun.com/j2se/1.5.0/docs/api/
https://maven-docs.mycompany.com/util/apidocs/
It works if configured like this:
maven-javadoc-plugin
ydoc.doclets.YStandard
C:/ydoc-3.0_01-jdk1.5/lib/ydoc.jar;C:/ydoc-3.0_01-jdk1.5/resources;${build.classes.dir}
-umlautogen -link
http://java.sun.com/j2se/1.5.0/docs/api/ -link
https://maven-docs.mycompany.com/util/apidocs/
--
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: (MJAVADOC-218) Ignoring links element in the configuration
[
http://jira.codehaus.org/browse/MJAVADOC-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150303#action_150303
]
Borut Bolcina commented on MJAVADOC-218:
I tried now by explicitly stating
org.apache.maven.plugins
maven-javadoc-plugin
2.5
and it seems it works! Can somebody confirm this?
> Ignoring links element in the configuration
> ---
>
> Key: MJAVADOC-218
> URL: http://jira.codehaus.org/browse/MJAVADOC-218
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Reporter: Borut Bolcina
>
> The links elements are ignored - here is the plugin configuration:
>
>
>
> maven-javadoc-plugin
>
> ydoc.doclets.YStandard
>
> C:/ydoc-3.0_01-jdk1.5/lib/ydoc.jar;C:/ydoc-3.0_01-jdk1.5/resources;${build.classes.dir}
> -umlautogen
>
> http://java.sun.com/j2se/1.5.0/docs/api/
>
> https://maven-docs.mycompany.com/util/apidocs/
>
>
>
> It works if configured like this:
>
>
>
> maven-javadoc-plugin
>
> ydoc.doclets.YStandard
>
> C:/ydoc-3.0_01-jdk1.5/lib/ydoc.jar;C:/ydoc-3.0_01-jdk1.5/resources;${build.classes.dir}
> -umlautogen -link
> http://java.sun.com/j2se/1.5.0/docs/api/ -link
> https://maven-docs.mycompany.com/util/apidocs/
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-639) log4j bad metadata
log4j bad metadata -- Key: MEV-639 URL: http://jira.codehaus.org/browse/MEV-639 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Borut Bolcina why there are no 1.2.14 and 1.2.15 versions in at http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml log4j log4j 1.1.3 1.1.3 1.2.4 1.2.5 1.2.6 1.2.7 1.2.8 1.2.11 1.2.9 1.2.12 1.2.13 -- 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: (MNGECLIPSE-105) Add maven-managed dependencies as project J2EE Module Dependencies
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_64494 ] Borut Bolcina commented on MNGECLIPSE-105: -- Hello, I am using Eclipse 3.2 RC2 with the latest (also RC2) Callisto update site modules (Web Standard Tools Version: 1.5.0.v200604030005-eYe38P_OHPq8Dcd) and Maven plugin 0.0.6 and having the same issue. Resolving this request would really boost dev cycle. Regards, Borut > Add maven-managed dependencies as project J2EE Module Dependencies > -- > > Key: MNGECLIPSE-105 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-105 > Project: Maven 2.x Extension for Eclipse > Type: Wish > Components: Dependency Resolver > Versions: 0.0.5 > Environment: Eclipse 3.1.2 with WTP 1.0, using Tomcat 5.5 for running webapp > projects. Maven 2.x Extension for Eclipse > Reporter: Daniel Fernández > Assignee: Eugene Kuleshov > Attachments: mngeclipse-test.zip > > > When creating a WTP's Dynamic Web project with eclipse, following a maven2 > directory structure and creating a pom.xml file for it using the Maven 2.x > Extension for Eclipse, everything works ok with dependencies as these are > added to the project build path (under the "Maven 2 Dependencies" folder) as > soon as they are added to the pom.xml > But, when this project is being run in a Tomcat Server from eclipse, these > dependencies are not being added to the WEB-INF/lib directory. This could be > done by adding, for each newly added dependency and its transitive > dependencies (not having scope "provided" or "test") an entry into the > ".settings/.component" file like these: > handle="module:/classpath/var/M2_REPO/commons-collections/commons-collections/2.1/commons-collections-2.1.jar"> > uses > > (this one was written by the maven-eclipse-plugin, which creates these > entries) > This way webapps created from eclipse and managed by maven could be > automatically run in Tomcat from Eclipse. > Regards, >Daniel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-393) Published artifacts should not depend on snapshot repos & artifacts
Published artifacts should not depend on snapshot repos & artifacts --- Key: MEV-393 URL: http://jira.codehaus.org/browse/MEV-393 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Borut Bolcina On behalf of Ingo: On 5/15/06, Weichsel, Ingo <[EMAIL PROTECTED]> wrote: > Hi, > > the doxia-site-renderer-1.0-alpha-8.pom does defines repositories, > > > > snapshots > http://snapshots.maven.codehaus.org/maven2 > > > > which can't be resolved. Any idea, if this will be fixed quickly, or do we > have to stick to the older plugin versions? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-104) There is no way to specify the input encoding of site documents
[ http://jira.codehaus.org/browse/MSITE-104?page=comments#action_65485 ] Borut Bolcina commented on MSITE-104: - I was eagerly awaiting this feature. Thanks! Writing documentation in UTF-8 works now, ... but menu items in site.xml still don't work. XML prolog is clearly stating for site.xml. This is not even neccessary, I think, as encoding is taken from maven-site-plugin 2.0-beta-5 UTF-8 UTF-8 So, it works in apt, xdoc and fml, but not in site.xml. > There is no way to specify the input encoding of site documents > > > Key: MSITE-104 > URL: http://jira.codehaus.org/browse/MSITE-104 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Naoki Nose > Assignee: Brett Porter > Fix For: 2.0-beta-5 > Attachments: doxia-input-encoding.diff, maven-site-plugin-input-encoding.diff > > > In Japan,it's necessary to specify the input encoding of site document > different from the system default, > because there is two commonly used encodings in Japanese > environment(Shift_JIS and EUC-JP). > But current maven-site-plugin doesn't provide the way to specify the input > encoding of site documents explicitly. > We need to specify it in POM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
