[M2]How to add a classpath entry without using dependencies
Hi Is it possible to add a single jar to the classpath (MANIFEST) of another jar, without using dependencies in Maven2? I can't use dependencies, because the jar which should be named in the classpath is not generated by Maven at the moment I generate the other jar. But it will be generated some projects later. So I'm looking for something like this: ... artifactIdmyFirstJar/artifactId packagingjar/packaging addToClasspathmySecondJar/addToClasspath ... Regards Sebastian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2]How to add a classpath entry without using dependencies
Hi I have a maybe very easy question, but I can't find it in the docu of Maven2. Is it possible to add a single jar to the classpath of another single jar, without using dependencies in Maven? I can't use dependencies, because the jar which should be named in the classpath is not generated by Maven at the moment I generate the other jar. But it will be generated some projects later. You can call it a ring-dependency. So I'm looking for somethings like this: ... artifactIdmyFirstJar/artifactId packagingjar/packaging addToClasspathmySecondJar/addToClasspath ... Regards Sebastian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Maven searches jars in wrong repository
Hi,
I've the following problem:
I have two repositories, one for releases and one for snapshots (
snapshotRepository ) specified in a parent-pom.
Deploying my artefact works fine. This means if I have a version like this
version1.0/version the artefact will be pumped into my normal repo.
And if I have one like this version1.0-SNAPSHOT/version it will be stored
in my snapshotRepository.
So far so good.
Next step: A second project of mine needs the above named artefact. (dependeny)
This dependency looks like
dependency
...
version[0.8,)/version
...
/dependency
This means get an version greater than 0.8.
I get following error while compile this second project:
Downloading:
http://{myServer}/internal/{groupId}/{artifactId}/1.0/{artifactId}-1.0.pom
Downloading:
http://{myServer}/snapshot/{groupId}/{artifactId}/1.0/{artifactId}-1.0.jar
It looks like Maven searches the pom on my internal repo and the belonging jar
on the snapshotRepo.
And for sure, Maven can't find the jar in the snapshotRepository.
Does anyone know something about this issue?
Mit freundlichem Gruß / Best Regards
Sebastian Krebs
QUIPSY QUALITY GmbH
Stuttgarter Strasse 23
D-75179 Pforzheim
[EMAIL PROTECTED]
[M2] TYPO in Docu about settings.xml regaring repositories and snapshots
Hello, I found following typo on http://maven.apache.org/maven-settings/settings.html Given : profile ... repositories repository release enabled/ updatePolicy/ checksumPolicy/ /release snapshot enabled/ updatePolicy/ checksumPolicy/ /snapshot id/ name/ url/ layout/ /repository /repositories ... /profile If you use this snapshot Maven will fail in reading the settings.xml You have to use snapshots ... /snapshots Mit freundlichem Gruß / Best Regards Sebastian Krebs QUIPSY QUALITY GmbH Stuttgarter Strasse 23 D-75179 Pforzheim [EMAIL PROTECTED]
AW: [M2- MVN Deploy Problem Error Code 201]
Hi,
now I get this, but I can make nothing of it :-)
Here is my stacktrace:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from QIR
[DEBUG] repository metadata for: 'snapshot xx.yy:zz:1.0.0-SNAPSHOT' could not
be found on repository: QIR
[DEBUG] not adding permissions to wagon connection
Uploading:
http://{myHost}/xx/yy/zz/1.0.0-SNAPSHOT/zz-1.0.0-20061016.051508-1.jar
25K uploaded
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection
returned the response code: 201
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection retur
ned the response code: 201
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection re
turned the response code: 201
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Unable to transfer file. Http
URLConnection returned the response code: 201
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:133)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Unable to transfer
file. HttpURLConnection returned the response code:
201
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:143)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Mon Oct 16 07:15:19 CEST 2006
[INFO] Final Memory: 5M/9M
[INFO]
Sebastian
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. Oktober 2006 16:45
An: Maven Users List
Betreff: Re: [M2- MVN Deploy Problem Error Code 201]
Try it again using mvn -X for additional debugging information that
might be useful.
Wayne
On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote:
Hi together,
I've got the following problem using M2.0.4
I want to deploy an artefact into my remote repository using mvn deploy.
Normally, or as I had understood, M2 will deploy the resulting jar and
the needed *.pom files.
When I'm calling mvn deploy, M2 only copies the resulting jar into my
repo.
After copying, M2 results in an error code of 201.
So M2 don't copy the other needed files, so further projects
[M2- MVN Deploy Problem Error Code 201]
Hi together, I've got the following problem using M2.0.4 I want to deploy an artefact into my remote repository using mvn deploy. Normally, or as I had understood, M2 will deploy the resulting jar and the needed *.pom files. When I'm calling mvn deploy, M2 only copies the resulting jar into my repo. After copying, M2 results in an error code of 201. So M2 don't copy the other needed files, so further projects will not find the artefact in my remote repo. Maybe Maven stops to copy the other files, because of getting an error while sending the first file ??? Did anyone know this problem ? Regards Sebastian Krebs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2]Creating a companywide POM
Hello, I've got the following question. I want to create a companywide Parent-pom.xml with all of those parameters and settings I will need in each project. e.g.: distributionManagement repository ... /repository /distributionManagement How can I inherit from my CompanyPOM? Regards Sebastian Krebs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Deploy into Remote Repository
Hello, I want to achieve the following: I have a remote repository on our local server and I want to say M2 that it has to deploy projects artefacts into this remote repository. But without configure this directly in each pom.xml, because we have multiple projects and for each the repository will be the same. Is this possible? Mit freundlichem Gruß / Best Regards Sebastian Krebs QUIPSY QUALITY GmbH Stuttgarter Strasse 23 D-75179 Pforzheim [EMAIL PROTECTED]
WG: [M2] Deploy into Remote Repository
Hello, I want to achieve the following: I have a remote repository on our local server and I want to say M2 that it has to deploy projects artefacts into this remote repository. But without configuring this directly in each pom.xml, because we have multiple projects and for each of them the repository will be the same. Is this possible? Mit freundlichem Gruß / Best Regards Sebastian Krebs QUIPSY QUALITY GmbH Stuttgarter Strasse 23 D-75179 Pforzheim [EMAIL PROTECTED]
