Hi,
Thanks for responding, I saw that I could use the plugin assembly. I'll try
to do it with this plugin :).
Thanks and regards
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-deploy-does-not-respect-finalName-tp5806549p5806658.html
Sent from the Maven Developers ma
Hello,
I dont think you can (or should) use arbitrary file names for artifacts
in a maven-style repository. They have to follow the
artifactid-classifier-version.type pattern.
It is usually the best to pack those files in an archive *-bin.zip or
similiar to keep their folder structure and file na
Hi,
When you run the maven deploy phase, maven upload to nexus the final file
with the name ${artifactId}-${version}, and does not respect the
set in the build.
How could I indicate to maven deploy plugin to upload to nexus with the
name, for example PREFIX_${artifactId}-${version}
Does anyone
Months ago, we had a discussion which, I believe, reached a consensus
to up the floor for components and plugins to 3.0.5. To be more
precise, to start to propagate that version for maven core
dependencies down the pom hierarchy. If someone had an itch to
maintain a branch of something that still s
+1
Regards,
Hervé
Le mercredi 24 septembre 2014 10:30:00 Benson Margulies a écrit :
> Hi,
>
> Here is release 15 of the POM we maintain for the entire ASF. The
> changes since release 14 can be seen here:
>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEAD&r2=157
> 5044&d
The Apache Maven team is pleased to announce the release of the
Apache Maven Clean Plugin, version 2.6
The Clean Plugin is used when you want to remove files generated at build-time
in a project's directory.
http://maven.apache.org/plugins/maven-clean-plugin/
You should specify the version in y
Hi,
The vote has passed with the following result:
+1 (binding): Karl-Heinz Marbaise, Jason van Zyl, Hervé Boutemy
+1 (non binding): Mirko Friedenhagen
I will promote the artifacts to the central repo.
Kind regards
Karl-Heinz Marbaise
--
+1
Regards,
Hervé
Le lundi 22 septembre 2014 08:58:13 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved N issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128&version=185
> 33
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=proj
+1
On Sep 25, 2014, at 3:08 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> i need more binding votes
>
> at least 2...
>
> Kind regards
> Karl-Heinz Marbaise
>
> On 9/22/14 8:58 AM, Karl Heinz Marbaise wrote:
>> Hi,
>>
>> We solved N issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa
Hi,
i need more binding votes
at least 2...
Kind regards
Karl-Heinz Marbaise
On 9/22/14 8:58 AM, Karl Heinz Marbaise wrote:
Hi,
We solved N issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128&version=18533
There are still a couple of issues left in JIRA:
http://jir
By the way, we were able to get the default wagon-http provider to work by
making a small change to the code from:
credentialsProvider.setCredentials( new AuthScope( host, port ), creds );
To:
// hardcoding for the test...
AuthScope authScope = new AuthScope(AuthScope.ANY_HOST, AuthScope.ANY_PO
On 25 Sep 2014, at 03:34, Igor Fedorenko wrote:
> No, you are not missing anything. We don't usually use the connector as
> build extension and there appear some sisu/guice related bugs that
> result in the exception you see.
I took a quick look and it’s not actually a bug in sisu/guice causing
I will forward you the details offline (as I am not comfortable forwarding
sensitive information to the mailing list).
--
Robert Patrick
VP, FMW Platform Engineering, Oracle Corporation
7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872
Frisco, TX 75034, USA Mobile: +1.469.556.94
Do you mind explaining what okhttp connector does wrong? I'd like this
usecase to work in m2e as this sounds like something many organization
would want to use.
I am setting up a test for this, but I don't know enough about http to
spot the problem. I am happy to share the test code if anyone is
We have looked at this wagon and it does not seem to address our problem.
What I would like to propose is that we go extend the existing Maven wagon-http
provider to allow configuration of the wagon to be able to support more
flexible scoping of the credentials than what is currently possible.
+1
On 24 September 2014 15:30, Benson Margulies wrote:
> Hi,
>
> Here is release 15 of the POM we maintain for the entire ASF. The
> changes since release 14 can be seen here:
>
>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEAD&r2=1575044&diff_format=h
>
> Staging repo:
>
+1
SHA1 of source package OK
Built plugin successfully using JDK 7 running `mvn323 -Prun-its
-DperformRelease=true verify`
Tested cleaning of a small project with mvn305 mvn311 mvn321 mvn322
mvn323 (JDK7)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
17 matches
Mail list logo