Hi all,
I have a project which maven generates the following output in the target
folder;
\projects\mywork\trunk\target\.jar
\projects\mywork\trunk\target\-sources.jar
\projects\mywork\trunk\target\installer\folder
The above installer\folder is basically an empty folder which contains
subfolders
On Sun, Jan 5, 2014 at 3:24 PM, Martin Gainty wrote:
>
> MG_01_05>Thanks for taking time to 'think this through'
>
More thinking and coding. Here's my final answer:
https://github.com/ljnelson/maven-artifacts/blob/master/src/main/java/com/edugility/maven/Artifacts.java#L80
That method builds th
> Here was the difference between the two job files:
Glad you followed up, I was going to ask to see the stuff that you had
snipped out, thinking you probably had ${...} or @ in it somewhere.
> The fact that there was only one '@' sign threw maven off and caused it to
> stop replacing subsequent
Here was the difference between the two job files:
a.job had this entry:
notify.emails=a...@adam.com,b...@bob.com
while b.job had this entry:
notify.emails=a...@adam.com
The fact that there was only one '@' sign threw maven off and caused it to
stop replacing subsequent properties in the same
On 8 January 2014 09:00, juliangeo wrote:
> Hi!
>
> I'm new to Maven and I've been struggling with this for a while. I just need
> to be able to programmatically build a project from a pom file in order to
> retrieve its relevant information. I am not using, nor want to, a maven
> plugin, just nee
Hi!
I'm new to Maven and I've been struggling with this for a while. I just need
to be able to programmatically build a project from a pom file in order to
retrieve its relevant information. I am not using, nor want to, a maven
plugin, just need this functionality as part of my application.
I've
Hi Omar,
Well, what Stephen advices *is* actually at least a part of the solution
you're looking for.
Stephen says you MUST NOT use the org.apache.maven.plugins and
maven-yourplugin-plugin naming scheme because this is a naming strategy
reserved for core maven plugins.
See the first section of
htt
Dear Maven users
I am one of the owners of Codehaus CARGO, which has a Maven2/Maven3
plugin; and would have a question with regards to how parameters are
managed.
We defined our MOJOs with parameters (you can see
http://svn.codehaus.org/cargo/extensions/trunk/maven2/plugin/src/main/java/org/codeh
FYI I call that a local aggregator pom. I typically set them up for the
various projects I jump between. I can then just open the whole set of
projects from intellij in one go and as this is maven I can safely discard
all the IDE's project info and have it regenerated from the pom and the
pom's rea
We are doing something similar with what I call an assembly project.
I have the following structure:
assembly
- pom.xml
- projectA
- pom.xml
- projectB
- pom.xml
- projectC
- pom.xml
- projectX
- pom.xml
Where the assembly's pom.xml contains like:
pom
projectA
p
Hi all mates,
I am having some troubles about how the methods in subject should behave,
due to the not exhaustive javadoc: given the artifact
com.acme:mycomponent:1.0
when invoking ArtifactRepository#find(Artifact) it always return an
artifact, even if it doesn';t exist in the target repo; given
11 matches
Mail list logo