Re: problem when deploying to nexus with a password with accent

[Gary Gregory]

Make sure the XML is saved in the encoding that matches the XML processing
instruction, usually UTF-8.

Gary

On Jun 16, 2017 7:57 AM, "djeanprost" 
wrote:

> Hello,
>
> I'm meeting a problem I can't deal with, and I hope someone here will help
> me find a solution.
>
> I want to deploy an artifact to my running nexus 2.14.x. I can log in nexus
> using my login/password. My password contains a french accent 'é'.
>
> When I fill my settings.xml with my clear password and its accent, I keep
> on
> receiving error 401 unauthorized from nexus when deploying.
> If I change my password in my ldap server, by removing the accent, and
> updating settings.xml, I can deploy my artifact. I udenrstand there is no
> problem with any nexus role.
> So now there is something wrong with my settings. Why is there a problem
> with a password containing an accent ?
>
> Thank you for your help.
> dom
>
>
>
> --
> View this message in context: http://maven.40175.n5.nabble.
> com/problem-when-deploying-to-nexus-with-a-password-with-
> accent-tp5910070.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

problem when deploying to nexus with a password with accent

[djeanprost]

Hello,

I'm meeting a problem I can't deal with, and I hope someone here will help
me find a solution.

I want to deploy an artifact to my running nexus 2.14.x. I can log in nexus
using my login/password. My password contains a french accent 'é'.

When I fill my settings.xml with my clear password and its accent, I keep on
receiving error 401 unauthorized from nexus when deploying.
If I change my password in my ldap server, by removing the accent, and
updating settings.xml, I can deploy my artifact. I udenrstand there is no
problem with any nexus role.
So now there is something wrong with my settings. Why is there a problem
with a password containing an accent ?

Thank you for your help.
dom



--
View this message in context: 
http://maven.40175.n5.nabble.com/problem-when-deploying-to-nexus-with-a-password-with-accent-tp5910070.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

ClassNotFoundException: org.sonatype.aether.collection.DependencyCollectionException

[Sergio Fernández]

Hi,

I'm suffering this issue, reported at
https://issues.apache.org/jira/browse/MARMOTTA-668

I found some details at
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound

But the information looks prety old. Does anybody has any hint how to some
this build issue?

Thanks in advance!

Cheers,

Re: Follow up: Building projects for multiple platforms

[Karl Heinz Marbaise]

Hi,

I would make a separate module for java8 and run there the retrolambda-
maven-plugin and another separate module for java7 and run there the 
retrolambda-

maven-plugin as well...than you can make a separate jar file for each ...

No need for different executions of the compiler plugins etc. and 
separte output folders configurations etc.


This needs to use toolchains and then you can run with a single 
run...all of them...


Just coming into my mind...



If i correctly understand you are developing in JDK 8 and than you would 
like to offer a package which supports JDK 7 ..


So making a module with JDK 8 code in it pluse unit tests...

A separate module which uses the JDK 8 code as dependency and using the 
retrolambda plugin and maybe some supplemental tests on it...using JDK 7 
which can be handled with Toolchain...



Kind regards
Karl Heinz Marbaise

On 16/06/17 14:25, Justin Georgeson wrote:

Instead of tweaking the version, I would configure an executions of the 
compiler plugins compile and testcompile goals to a separate output folders, 
like ${build.directory}${file.separator}classes-java7 and 
${build.directory}${file.separator}test-classes-java7 and then an execution of 
the jar plugin to create/attach a jar with classifier set to 'java7'.

https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html

That way you can have both versions build/deploy together in one pipeline with 
the same version.

You can use properties in the version if you use Maven 3.5 with some other 
tricks, there was a recent thread on the list about it

http://www.mail-archive.com/users@maven.apache.org/msg139475.html



-Original Message-
From: Christofer Dutz [mailto:christofer.d...@c-ware.de]
Sent: Friday, June 16, 2017 3:54 AM
To: Maven List 
Subject: [EXTERNAL] Follow up: Building projects for multiple platforms

External Sender: Use caution with links/attachments.



Hi,

A short follow up question regarding my last one.
In the Edgent maven build, which I am working on, we need to produce java8,
java7 and android versions of jars. This is done by running the retrolambda-
maven-plugin on the classes when building the java7 version. To make the
dependency resolution work correctly with all variants we decided to use the
normal version number for the java8 output and add a suffix of “–java7” to the
version in case of a java7 build (for SNAPSHOT versions the “-java7” is included
between the version and the “SNAPSHOT”). In order to be able to switch the
versions by selecting profiles, I used variables for the artifact versions.
As I know variables for versions of parent poms is a really bad idea (Don’t even
know if it works), I setup the project to have constant versions in the parent
poms and only use these for configuring the reactor and the plugins – no
dependencies are handled here. The build is working nicey, unfortunately the
build is outputting hundreds of warnings like this:

[WARNING] Some problems were encountered while building the effective model
for org.apache.edgent.analytics:edgent-analytics-sensors:jar:1.2.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @
org.apache.edgent.analytics:edgent-analytics-sensors:${edgent.version},
/Users/christoferdutz/Projects/Apache/Edgent/incubator-
edgent/analytics/sensors/pom.xml, line 31, column 12

Is there a “maven way” (TM) to achieve this sort of thing without the warnings?

Chris


--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Follow up: Building projects for multiple platforms

[Justin Georgeson]

Instead of tweaking the version, I would configure an executions of the 
compiler plugins compile and testcompile goals to a separate output folders, 
like ${build.directory}${file.separator}classes-java7 and 
${build.directory}${file.separator}test-classes-java7 and then an execution of 
the jar plugin to create/attach a jar with classifier set to 'java7'.

https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html

That way you can have both versions build/deploy together in one pipeline with 
the same version. 

You can use properties in the version if you use Maven 3.5 with some other 
tricks, there was a recent thread on the list about it

http://www.mail-archive.com/users@maven.apache.org/msg139475.html


> -Original Message-
> From: Christofer Dutz [mailto:christofer.d...@c-ware.de]
> Sent: Friday, June 16, 2017 3:54 AM
> To: Maven List 
> Subject: [EXTERNAL] Follow up: Building projects for multiple platforms
> 
> External Sender: Use caution with links/attachments.
> 
> 
> 
> Hi,
> 
> A short follow up question regarding my last one.
> In the Edgent maven build, which I am working on, we need to produce java8,
> java7 and android versions of jars. This is done by running the retrolambda-
> maven-plugin on the classes when building the java7 version. To make the
> dependency resolution work correctly with all variants we decided to use the
> normal version number for the java8 output and add a suffix of “–java7” to the
> version in case of a java7 build (for SNAPSHOT versions the “-java7” is 
> included
> between the version and the “SNAPSHOT”). In order to be able to switch the
> versions by selecting profiles, I used variables for the artifact versions.
> As I know variables for versions of parent poms is a really bad idea (Don’t 
> even
> know if it works), I setup the project to have constant versions in the parent
> poms and only use these for configuring the reactor and the plugins – no
> dependencies are handled here. The build is working nicey, unfortunately the
> build is outputting hundreds of warnings like this:
> 
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.edgent.analytics:edgent-analytics-sensors:jar:1.2.0-SNAPSHOT
> [WARNING] 'version' contains an expression but should be a constant. @
> org.apache.edgent.analytics:edgent-analytics-sensors:${edgent.version},
> /Users/christoferdutz/Projects/Apache/Edgent/incubator-
> edgent/analytics/sensors/pom.xml, line 31, column 12
> 
> Is there a “maven way” (TM) to achieve this sort of thing without the 
> warnings?
> 
> Chris

--
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: WELCOME to users@maven.apache.org

[Dave Brosius]

Greetings,

I have a custom maven plugin that uses MavenProject to 
getCompileDependencies() on. This works fine. But now i realize that I 
want to get all the dependencies for a multi module pom. So i use,


@Parameter(property = "reactorProjects", readonly = true, 
required = true)

private List reactorProjects;

This injection seems to work, as i'm able to get attributes from each, 
like output directory.




However, when i ask for getCompileDependencies(); for these reactor 
projects, nothing is returned.


Any idea what i could be doing wrong, or is there another way of doing 
this?



Code here. 
https://github.com/mebigfatguy/fbp-maven-plugin/blob/master/src/main/java/com/mebigfatguy/fbp/FBPMojo.java



thanks,
dave

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Follow up: Building projects for multiple platforms

[Christofer Dutz]

Hi,

A short follow up question regarding my last one.
In the Edgent maven build, which I am working on, we need to produce java8, 
java7 and android versions of jars. This is done by running the 
retrolambda-maven-plugin on the classes when building the java7 version. To 
make the dependency resolution work correctly with all variants we decided to 
use the normal version number for the java8 output and add a suffix of “–java7” 
to the version in case of a java7 build (for SNAPSHOT versions the “-java7” is 
included between the version and the “SNAPSHOT”). In order to be able to switch 
the versions by selecting profiles, I used variables for the artifact versions.
As I know variables for versions of parent poms is a really bad idea (Don’t 
even know if it works), I setup the project to have constant versions in the 
parent poms and only use these for configuring the reactor and the plugins – no 
dependencies are handled here. The build is working nicey, unfortunately the 
build is outputting hundreds of warnings like this:

[WARNING] Some problems were encountered while building the effective model for 
org.apache.edgent.analytics:edgent-analytics-sensors:jar:1.2.0-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ 
org.apache.edgent.analytics:edgent-analytics-sensors:${edgent.version}, 
/Users/christoferdutz/Projects/Apache/Edgent/incubator-edgent/analytics/sensors/pom.xml,
 line 31, column 12

Is there a “maven way” (TM) to achieve this sort of thing without the warnings?

Chris