You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Greg Akins <an...@gmail.com> on 2010/05/28 19:26:41 UTC
Mavenizing a project
I'm working on Mavenizing a small project. In the current project,
there are three "source" directories.
The Main source, the JUnit test source and a dir called
"test_informal" that contains some "helper" classes for doing
interactive testing...
In a maven project, where would one put that type of source?
--
Greg Akins
http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Mavenizing a project
Posted by Wayne Fay <wa...@gmail.com>.
> If you don't use that little trick, project B cannot depend on project
> A for it's test classes because the final artifacts never contain test classes.
That is one way to do it... but I'd suggest the test-jar approach:
http://maven.apache.org/guides/mini/guide-attached-tests.html
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Mavenizing a project
Posted by Brian Topping <to...@codehaus.org>.
Put your tests in src/test/java as normal.
If your helper classes are to be used by multiple projects, create a new project just for the helper classes, call it foo-test or something. Put the helper classes in src/main/java in the foo-test project, not src/test/main. Then you can create a dependency with test scope on foo-test from the projects that need the test helper classes.
If you don't use that little trick, project B cannot depend on project A for it's test classes because the final artifacts never contain test classes.
Brian
On May 28, 2010, at 1:26 PM, Greg Akins wrote:
> I'm working on Mavenizing a small project. In the current project,
> there are three "source" directories.
>
> The Main source, the JUnit test source and a dir called
> "test_informal" that contains some "helper" classes for doing
> interactive testing...
>
> In a maven project, where would one put that type of source?
>
> --
> Greg Akins
>
> http://insomnia-consulting.org
> http://www.pghcodingdojo.org
> http://pittjug.dev.java.net
> http://twitter.com/akinsgre
> http://www.linkedin.com/in/akinsgre
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Mavenizing a flex project
Posted by Jeff MAURY <je...@jeffmaury.com>.
See riadiscuss.jeffmaury.com but the tutorial is for Flex Builder 3 projects.
Jeff MAURY
On Saturday, May 29, 2010, Viv Kapadekar <vi...@peoplepowerco.com> wrote:
> Has anyone mavenized a flex ( flash 4) project?
>
> Thx,
> Viv
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Mavenizing a flex project
Posted by Marvin Froeder <ve...@gmail.com>.
Well, we don't have a specific set of instructions to mavenize a
pre-existing project. But the getting started will most likely help your.
http://flexmojos.sonatype.org/getting-started.html
VELO
On Sat, May 29, 2010 at 5:11 AM, Viv Kapadekar <vi...@peoplepowerco.com>wrote:
> Has anyone mavenized a flex ( flash 4) project?
>
> Thx,
> Viv
>
>
>
>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Mavenizing a flex project
Posted by Viv Kapadekar <vi...@peoplepowerco.com>.
Has anyone mavenized a flex ( flash 4) project?
Thx,
Viv
>
>>
>>
>>
>>>
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Mavenizing a project
Posted by Martin Gainty <mg...@hotmail.com>.
one is re-factoring your ANT taskdef class into a Mojo
path of least resistance is to stick with antrun
http://maven.apache.org/plugins/maven-antrun-plugin/
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Fri, 28 May 2010 14:56:37 -0400
> Subject: Re: Mavenizing a project
> From: sfrancolla@gmail.com
> To: angrygreg@gmail.com
> CC: users@maven.apache.org
>
> My experience has consistently been that if I adapt my projects to Maven
> instead of vice-versa, life is just peachy. Have yet to come across a
> circumstance in Maven that hasn't already been solved for. Just go with it.
>
>
> On Fri, May 28, 2010 at 2:04 PM, Greg Akins <an...@gmail.com> wrote:
>
> > On Fri, May 28, 2010 at 1:43 PM, Steve Francolla <sf...@gmail.com>
> > wrote:
> > > My advice is to fit your needs into Maven's standard directory layout
> > > (project structure).
> > >
> > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> > > Your main source and junit source will fit well there. Unsure how your
> > > helper classes fit in but it seems to me that the case can probably be
> > made
> > > for that to be packaged within the test source branch as well.
> > >
> >
> > That seems like it might work better for my team. I think I'll have a
> > bit more of a fight if I have to create a separate project. And truth
> > is, I don't even think these tests get executed anymore. I just need
> > to keep them intact until I can replace them with something better.
> >
> > --
> > Greg Akins
> >
> > http://insomnia-consulting.org
> > http://www.pghcodingdojo.org
> > http://pittjug.dev.java.net
> > http://twitter.com/akinsgre
> > http://www.linkedin.com/in/akinsgre
> >
_________________________________________________________________
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
Re: Mavenizing a project
Posted by Steve Francolla <sf...@gmail.com>.
My experience has consistently been that if I adapt my projects to Maven
instead of vice-versa, life is just peachy. Have yet to come across a
circumstance in Maven that hasn't already been solved for. Just go with it.
On Fri, May 28, 2010 at 2:04 PM, Greg Akins <an...@gmail.com> wrote:
> On Fri, May 28, 2010 at 1:43 PM, Steve Francolla <sf...@gmail.com>
> wrote:
> > My advice is to fit your needs into Maven's standard directory layout
> > (project structure).
> >
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> > Your main source and junit source will fit well there. Unsure how your
> > helper classes fit in but it seems to me that the case can probably be
> made
> > for that to be packaged within the test source branch as well.
> >
>
> That seems like it might work better for my team. I think I'll have a
> bit more of a fight if I have to create a separate project. And truth
> is, I don't even think these tests get executed anymore. I just need
> to keep them intact until I can replace them with something better.
>
> --
> Greg Akins
>
> http://insomnia-consulting.org
> http://www.pghcodingdojo.org
> http://pittjug.dev.java.net
> http://twitter.com/akinsgre
> http://www.linkedin.com/in/akinsgre
>
Re: Mavenizing a project
Posted by Greg Akins <an...@gmail.com>.
On Fri, May 28, 2010 at 1:43 PM, Steve Francolla <sf...@gmail.com> wrote:
> My advice is to fit your needs into Maven's standard directory layout
> (project structure).
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> Your main source and junit source will fit well there. Unsure how your
> helper classes fit in but it seems to me that the case can probably be made
> for that to be packaged within the test source branch as well.
>
That seems like it might work better for my team. I think I'll have a
bit more of a fight if I have to create a separate project. And truth
is, I don't even think these tests get executed anymore. I just need
to keep them intact until I can replace them with something better.
--
Greg Akins
http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Mavenizing a project
Posted by Steve Francolla <sf...@gmail.com>.
My advice is to fit your needs into Maven's standard directory layout
(project structure).
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
Your main source and junit source will fit well there. Unsure how your
helper classes fit in but it seems to me that the case can probably be made
for that to be packaged within the test source branch as well.
SF
On Fri, May 28, 2010 at 1:26 PM, Greg Akins <an...@gmail.com> wrote:
> I'm working on Mavenizing a small project. In the current project,
> there are three "source" directories.
>
> The Main source, the JUnit test source and a dir called
> "test_informal" that contains some "helper" classes for doing
> interactive testing...
>
> In a maven project, where would one put that type of source?
>
> --
> Greg Akins
>
> http://insomnia-consulting.org
> http://www.pghcodingdojo.org
> http://pittjug.dev.java.net
> http://twitter.com/akinsgre
> http://www.linkedin.com/in/akinsgre
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>