Re: maven compiler plugin + toolchains

[Jörg Schaible]

intel radoux wrote:

> Hello,
> 
> Yes, I could use "maven.compiler.source"  properties, but i'm on a parent
> pom, and if somebody add a configuration like
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 3.3
> 
> xxx
> xxx
> 
> 
> 
> on his module it will fail.
> 
> I was wondering if there was some kind of auto-link between source level
> in maven-compiler-plugin and toolchain plugin (it would be nice)
> 
> Anyway, I will go with this solution and hope for the best (anyway I will
> set the default jdk version to 1.5 so that if somebody update the source
> level by itself (not by the maven.compiler.source if will fail hard :D )

Define the plugin configuration in the parent pom in a pluginMgmt section 
and use the proposed property. Someone who inherits the POM may simply 
redefine the property then.

Cheers,
Jörg



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

Re: maven compiler plugin + toolchains

[intel radoux]

Hello,

Yes, I could use "maven.compiler.source"  properties, but i'm on a parent
pom, and if somebody add a configuration like


org.apache.maven.plugins
maven-compiler-plugin
3.3

xxx
xxx



on his module it will fail.

I was wondering if there was some kind of auto-link between source level in
maven-compiler-plugin and toolchain plugin (it would be nice)

Anyway, I will go with this solution and hope for the best (anyway I will
set the default jdk version to 1.5 so that if somebody update the source
level by itself (not by the maven.compiler.source if will fail hard :D )

2015-04-22 20:56 GMT+02:00 Ron Wheeler :

> Would setting a property ( 1.6
> ) in your parent and using the property as the
> value ($java_compliance_version )in the source, work?
>
> Ron
>
>
>
> On 22/04/2015 2:42 PM, intel radoux wrote:
>
>> Hello,
>>
>> I wish to set something like this in my parent pom :
>>
>> 
>>  org.apache.maven.plugins
>>  maven-compiler-plugin
>>  3.3
>>  
>>  1.6
>>  1.6
>>  
>>  
>>  
>>  org.apache.maven.plugins
>>  maven-toolchains-plugin
>>  1.1
>>  
>>  
>>  
>>
>>
>> ${project.build.pluginsAsMap(org.apache.maven.plugins:maven-compiler-plugin).configuration.children[0].value}
>>
>>  
>>  
>>  
>>  
>>  
>>  
>>  toolchain
>>  
>>  
>>  
>>  
>>
>> so that I can only set the source level in one place. The idea is that I
>> can set another level in one child module and toolchain will select the
>> correct JDK.
>>   
>>  org.apache.maven.plugins
>>  maven-compiler-plugin
>>  3.3
>>  
>>  1.7
>>  1.7
>>  
>>  
>>
>> unfortunatly this don't work has ${project.build... } is not resolved
>> when set in configuration element.
>> Do somebody have another idea on how to set this ? (why toolchain doesn't
>> work hand on hand with compiler plugins ? )
>>
>> Thank you
>>
>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Apache Maven & ANT - VPAT

[Jim Klo]

Actually there may be some relevance.

There are some services that could be used to automate 508 and other A11y 
compliance. For example, you could execute a workflow during the test phase 
that validates content against the IDI Web Accessibility Checker 
(http://achecker.ca/checker/index.php  
and https://github.com/inclusive-design/AChecker 
). But in this case maven doesn’t 
really have any direct connection to validating 508 - it’s just a tool that 
coordinates some other service as part of a larger workflow.

Aside from specific modules that generate web content (such as Javadoc) that is 
likely the extent to which 508 would apply.

This same statement would apply to really any configuration management solution 
like Maven (CMake, Gradle, Ivy, etc).

> On Apr 23, 2015, at 7:33 AM, Benson Margulies  wrote:
> 
> I cannot imagine how anyone could expect a command-line tool for software
> developers to be relevant to 508. We've never considered the question for
> Maven and I don't think that we ever will. You might look into how people
> treat, for example, 'make' as an model.
> 
> 
> 
> On Thu, Apr 23, 2015 at 9:34 AM,  wrote:
> 
>> Hi Apache Team – Apache Maven & ANT are 2 products being used by
>> Accenture for a client project. We need your assistance in verifying the
>> VPAT status for these 2 products.
>> 
>> 
>> 
>> I found the below statement in the community discussion area. Can you
>> confirm this is correct and VPAT does not actually apply to Apache? Below I
>> have also included a brief description of the U.S Federal VPAT purpose.
>> 
>> 
>> 
>> "Apache doesn't have anything to do with the accessibility. It just
>> provides the web pages which can be accessible or not accessible at all.508
>> compliance applies to a site (or a page), not to a server.”
>> 
>> 
>> 
>> *The purpose of the Voluntary Product Accessibility Template, or VPAT, is
>> to assist Federal contracting officials and other buyers in making
>> preliminary assessments regarding the availability of commercial
>> “Electronic and Information Technology” products and services with features
>> that support accessibility. *
>> 
>> 
>> 
>> *The Voluntary Product Accessibility Template (VPAT) is a document which
>> evaluates how accessible a particular product is according to the Section
>> 508 Standards. It is a self-disclosing document produced by the vendor
>> which details each aspect of the Section 508 requirements and how the
>> product supports each criteria.*
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> *Amber Akins*
>> 
>> *Client & Sales Support*
>> 
>> *Accenture - Alliance Services*
>> 
>> *e-mail:  amber.l.ak...@accenture.com *
>> 
>> *Phone: 678-657-2250 <678-657-2250>*
>> 
>> *Fax: **678-657-0043 <678-657-0043>*
>> 
>> 
>> 
>> --
>> 
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you have
>> received it in error, please notify the sender immediately and delete the
>> original. Any other use of the e-mail by you is prohibited. Where allowed
>> by local law, electronic communications with Accenture and its affiliates,
>> including e-mail and instant messaging (including content), may be scanned
>> by our systems for the purposes of information security and assessment of
>> internal compliance with Accenture policy.
>> 
>> __
>> 
>> www.accenture.com
>> 




smime.p7s
Description: S/MIME cryptographic signature

Re: Apache Maven & ANT - VPAT

[trasukg]

Seems reasonable to ask how accessible the website / documents are, though. 

Greg Trasuk 


Sent from my BlackBerry 10 smartphone.
  Original Message  
From: Benson Margulies
Sent: Thursday, April 23, 2015 10:33 AM
To: amber.l.ak...@accenture.com; Maven Users List
Reply To: Maven Users List
Subject: Re: Apache Maven & ANT - VPAT

I cannot imagine how anyone could expect a command-line tool for software
developers to be relevant to 508. We've never considered the question for
Maven and I don't think that we ever will. You might look into how people
treat, for example, 'make' as an model.



On Thu, Apr 23, 2015 at 9:34 AM,  wrote:

> Hi Apache Team – Apache Maven & ANT are 2 products being used by
> Accenture for a client project. We need your assistance in verifying the
> VPAT status for these 2 products.
>
>
>
> I found the below statement in the community discussion area. Can you
> confirm this is correct and VPAT does not actually apply to Apache? Below I
> have also included a brief description of the U.S Federal VPAT purpose.
>
>
>
> "Apache doesn't have anything to do with the accessibility. It just
> provides the web pages which can be accessible or not accessible at all.508
> compliance applies to a site (or a page), not to a server.”
>
>
>
> *The purpose of the Voluntary Product Accessibility Template, or VPAT, is
> to assist Federal contracting officials and other buyers in making
> preliminary assessments regarding the availability of commercial
> “Electronic and Information Technology” products and services with features
> that support accessibility. *
>
>
>
> *The Voluntary Product Accessibility Template (VPAT) is a document which
> evaluates how accessible a particular product is according to the Section
> 508 Standards. It is a self-disclosing document produced by the vendor
> which details each aspect of the Section 508 requirements and how the
> product supports each criteria.*
>
>
>
>
>
>
>
> *Amber Akins*
>
> *Client & Sales Support*
>
> *Accenture - Alliance Services*
>
> *e-mail: amber.l.ak...@accenture.com *
>
> *Phone: 678-657-2250 <678-657-2250>*
>
> *Fax: **678-657-0043 <678-657-0043>*
>
>
>
> --
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>

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

Re: Adding comments to dependencies in POM

[Ron Wheeler]

On 23/04/2015 4:32 AM, Tomasz Borek wrote:

I'm actually quite surprised by this thread. My perspective on adding a
comment tag is different to most here:

A)nother tag in XML *MIGHT* help with letting me know why XYZ was added. IF
people will remember to fill it out. And XYZ removal cuts out the comment
as well, so if somebody removed a dependency / other I was relying on, I'm
no smarter.
If the person read the comment and still deleted the dependency, at 
least they knew what the impact would be on the build.
One has to assume that people who are allowed to change software are 
responsible.

B)loated / bigger XML, another tag to fill in, for each dependency, yay! :/
I would only use it where the need for the dependency is obscure or as 
in my example Use Case 2 the version can not be changed for a known 
reason that might not be known by others.

You are right that putting useless comments would not be helpful.


C)hanges monitoring is what SCM is designed for. Just have your POM under
version control and you'll see when what and why was removed/changed/added.
Hoping to avoid a retrospective analysis and search for a perpetrator by 
letting people know in advance that the pom statements that look like 
they should be fixed, are actually there for a reason.




For me the idea ain't appealing, it's actually slightly on the "no, I don't
want" side.

pozdrawiam,
LAFK

2015-04-21 0:31 GMT+02:00 Jim Klo :


On Apr 20, 2015, at 2:38 PM, Ron Wheeler 
wrote:

On 20/04/2015 4:55 PM, Jim Klo wrote:

Comments inline below..

On Apr 20, 2015, at 10:44 AM, Ron Wheeler mailto:rwhee...@artifact-software.com >>
wrote:

RDF sounds like overkill. There is no reason why a comment could not be a
URI but I am not sure that you want to mandate that.
Use Case 1 link to web resource
http://blog.artifact-software.com/tech/?p=191”>


Having dealt with this sort of thing on other projects, linked comments
sound good at first but ultimately become a very bad idea IMO. This creates
a non-idempotent and brittle link scenario where the comment url is out of
synch with the content in the POM.


Use Case 2 lots of in-line deatils
   
   org.apache.xmlgraphics
   fop
   1.0
   true
   

Use case 3 reference to a full explanation in the description
There is also the description tag which could be used to hold more details
   http://maven.apache.org/comments/1.0.0”>
…

http://example.com/foo-123
)”>



Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec et
vestibulum odio, at porttitor nunc. Donec pulvinar erat quis accumsan
interdum. Nunc at viverra nunc. Mauris purus ipsum, aliquam vitae nisi
eget, faucibus auctor leo. Duis ipsum leo, viverra eleifend viverra in,
tristique vitae tortor. Interdum et malesuada fames ac ante ipsum primis in
faucibus. Suspendisse tempus nisl dui, at rutrum massa porta id.
Suspendisse ultricies est vel pretium egestas. In orci ipsum, vehicula non
accumsan quis, pellentesque ac ipsum. Maecenas maximus ornare tempus. Fusce
libero ligula, tempor mattis pretium et, consectetur ut sapien. Aliquam
rhoncus lorem erat. Nullam et.



Are you proposing that comment tags be allowed inside all tags or just
some.

I would suggest comment attributes on all elements.


I would vote for a comment element to be a child of any tag and a comment
attribute be available on all elements. However when considering a more
global solution, I would think adding a specific namespace for comments
makes a whole lot more sense and would be a more portable solution and
avoid collisions with existing plug-ins. IMO it’s easier to update base
parsers to disregard elements from foreign namespaces than to hope to avoid
collisions with existing plug-ins.  However that’s a gut feeling without
doing any investigation as to what the scope of impact a change like that
would really mean. If it really isn't a huge problem to just add comments
to the POM namespace, that would be my #1 choice.








--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


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

Re: Apache Maven & ANT - VPAT

[Benson Margulies]

I cannot imagine how anyone could expect a command-line tool for software
developers to be relevant to 508. We've never considered the question for
Maven and I don't think that we ever will. You might look into how people
treat, for example, 'make' as an model.



On Thu, Apr 23, 2015 at 9:34 AM,  wrote:

>  Hi Apache Team – Apache Maven & ANT are 2 products being used by
> Accenture for a client project. We need your assistance in verifying the
> VPAT status for these 2 products.
>
>
>
> I found the below statement in the community discussion area. Can you
> confirm this is correct and VPAT does not actually apply to Apache? Below I
> have also included a brief description of the U.S Federal VPAT purpose.
>
>
>
> "Apache doesn't have anything to do with the accessibility. It just
> provides the web pages which can be accessible or not accessible at all.508
> compliance applies to a site (or a page), not to a server.”
>
>
>
> *The purpose of the Voluntary Product Accessibility Template, or VPAT, is
> to assist Federal contracting officials and other buyers in making
> preliminary assessments regarding the availability of commercial
> “Electronic and Information Technology” products and services with features
> that support accessibility. *
>
>
>
> *The Voluntary Product Accessibility Template (VPAT) is a document which
> evaluates how accessible a particular product is according to the Section
> 508 Standards. It is a self-disclosing document produced by the vendor
> which details each aspect of the Section 508 requirements and how the
> product supports each criteria.*
>
>
>
>
>
>
>
> *Amber Akins*
>
> *Client & Sales Support*
>
> *Accenture - Alliance Services*
>
> *e-mail:  amber.l.ak...@accenture.com *
>
> *Phone: 678-657-2250 <678-657-2250>*
>
> *Fax: **678-657-0043 <678-657-0043>*
>
>
>
> --
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>

Re: Adding comments to dependencies in POM

[Tomasz Borek]

I'm actually quite surprised by this thread. My perspective on adding a
comment tag is different to most here:

A)nother tag in XML *MIGHT* help with letting me know why XYZ was added. IF
people will remember to fill it out. And XYZ removal cuts out the comment
as well, so if somebody removed a dependency / other I was relying on, I'm
no smarter.
B)loated / bigger XML, another tag to fill in, for each dependency, yay! :/
C)hanges monitoring is what SCM is designed for. Just have your POM under
version control and you'll see when what and why was removed/changed/added.

For me the idea ain't appealing, it's actually slightly on the "no, I don't
want" side.

pozdrawiam,
LAFK

2015-04-21 0:31 GMT+02:00 Jim Klo :

>
> On Apr 20, 2015, at 2:38 PM, Ron Wheeler 
> wrote:
>
> On 20/04/2015 4:55 PM, Jim Klo wrote:
>
> Comments inline below..
>
> On Apr 20, 2015, at 10:44 AM, Ron Wheeler  >
> wrote:
>
> RDF sounds like overkill. There is no reason why a comment could not be a
> URI but I am not sure that you want to mandate that.
> Use Case 1 link to web resource
> http://blog.artifact-software.com/tech/?p=191”>
>
>
> Having dealt with this sort of thing on other projects, linked comments
> sound good at first but ultimately become a very bad idea IMO. This creates
> a non-idempotent and brittle link scenario where the comment url is out of
> synch with the content in the POM.
>
>
> Use Case 2 lots of in-line deatils
>   
>   org.apache.xmlgraphics
>   fop
>   1.0
>   true
>   
>
> Use case 3 reference to a full explanation in the description
> There is also the description tag which could be used to hold more details
>   http://maven.apache.org/comments/1.0.0”>
> …
>
> http://example.com/foo-123
> )”>
>
> 
> 
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec et
> vestibulum odio, at porttitor nunc. Donec pulvinar erat quis accumsan
> interdum. Nunc at viverra nunc. Mauris purus ipsum, aliquam vitae nisi
> eget, faucibus auctor leo. Duis ipsum leo, viverra eleifend viverra in,
> tristique vitae tortor. Interdum et malesuada fames ac ante ipsum primis in
> faucibus. Suspendisse tempus nisl dui, at rutrum massa porta id.
> Suspendisse ultricies est vel pretium egestas. In orci ipsum, vehicula non
> accumsan quis, pellentesque ac ipsum. Maecenas maximus ornare tempus. Fusce
> libero ligula, tempor mattis pretium et, consectetur ut sapien. Aliquam
> rhoncus lorem erat. Nullam et.
> 
> 
>
> Are you proposing that comment tags be allowed inside all tags or just
> some.
>
> I would suggest comment attributes on all elements.
>
>
> I would vote for a comment element to be a child of any tag and a comment
> attribute be available on all elements. However when considering a more
> global solution, I would think adding a specific namespace for comments
> makes a whole lot more sense and would be a more portable solution and
> avoid collisions with existing plug-ins. IMO it’s easier to update base
> parsers to disregard elements from foreign namespaces than to hope to avoid
> collisions with existing plug-ins.  However that’s a gut feeling without
> doing any investigation as to what the scope of impact a change like that
> would really mean. If it really isn't a huge problem to just add comments
> to the POM namespace, that would be my #1 choice.
>
>
>
>
>

Re: Running ALL tests in a multi-module , then failing the entire build.

[Stephen Connolly]

You probably want to also set

-DingnoreTestFailures

Or whatever it is called as those fail-at-end and fail-never just affect
the overall result. If an individual module fails during "test" it will
never get to "package" and the inter-module dependencies may not behave the
same (jar files behave differently from target/classes) or may be missing
(may be producing a war file to be consumed by an integration test module)

IMHO you want both

On Thursday, April 23, 2015, Mark Derricutt  wrote:

> On 23 Apr 2015, at 17:12, Kevin Burton wrote:
>
> > My understanding , is that I can enable this, but then the result of the
> > run is a successful build?  Is that true?
> >
> > what’s the easiest way to set this up?
>
> You could use:
>
>   mvn --fail-at-end
>
> which will run all modules regardless of if any fail, and only fail the
> "build" at the end.
>
> or
>
>   mvn --fail-never
>
> if you want to run everything, but have the build "succeed" and some other
> process looks at the logs...
>
> Does that help?
>
> Mark
>
> --
> Mark Derricutt
> http://www.theoryinpractice.net
> http://www.chaliceofblood.net
> http://plus.google.com/+MarkDerricutt
> http://twitter.com/talios
> http://facebook.com/mderricutt
>


-- 
Sent from my phone