On Mon, Sep 19, 2011 at 9:18 PM, sebb wrote:
>> I don't think the meta-information about locations is available to
>> Maven from the plugins, each plugin defines its own configuration and
>> Maven doesn't interpret that in anyway.
>> You would have to bake each plugin's default layouts into your
>
On 19 September 2011 03:49, Barrie Treloar wrote:
> On Mon, Sep 19, 2011 at 10:56 AM, sebb wrote:
>>> The standard directories layout
>>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>>> lists what you are looking for.
>>
>> It lists only some of
On Mon, Sep 19, 2011 at 10:56 AM, sebb wrote:
>> The standard directories layout
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>> lists what you are looking for.
>
> It lists only some of the standard files and paths.
> For example it does not li
On 19 September 2011 01:01, Barrie Treloar wrote:
> On Sun, Sep 18, 2011 at 9:39 PM, sebb wrote:
>> Is there a plugin which can be used to check that a project is using
>> the standard Maven directory layout?
>>
>> For example, src/main/java rather than src/java; src/changes/changes.xml etc.
>>
>
On Sun, Sep 18, 2011 at 9:39 PM, sebb wrote:
> Is there a plugin which can be used to check that a project is using
> the standard Maven directory layout?
>
> For example, src/main/java rather than src/java; src/changes/changes.xml etc.
>
> AFAICT. the verifier plugin could be used for this, but:
Is there a plugin which can be used to check that a project is using
the standard Maven directory layout?
For example, src/main/java rather than src/java; src/changes/changes.xml etc.
AFAICT. the verifier plugin could be used for this, but:
1) the rules would have to be defined
2) the rules file
).
++
Julien
- Message d'origine
> De : Richard Hauswald
> À : users@maven.apache.org
> Envoyé le : Mer 18 Novembre 2009, 13 h 09 min 35 s
> Objet : WTP support and Standard Directory Layout
>
> Hello list,
> as described in the Standard Directory Layout
> (h
21 PM, Anders Hammar
>> wrote:
>> >> > Is this a Maven question or an Eclipse (WTP) question? The subject
>> says
>> >> WTP
>> >> > so I wonder what build path you're referring to.
>> >> >
>> >> > /Anders
&
;> > so I wonder what build path you're referring to.
> >> >
> >> > /Anders
> >> >
> >> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
> >> > richard.hausw...@googlemail.com> wrote:
> >> >
> >> >> Hello lis
subject says
>> WTP
>> > so I wonder what build path you're referring to.
>> >
>> > /Anders
>> >
>> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
>> > richard.hausw...@googlemail.com> wrote:
>> >
>> &g
ven question or an Eclipse (WTP) question? The subject says
> WTP
> > so I wonder what build path you're referring to.
> >
> > /Anders
> >
> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
> > richard.hausw...@googlemail.com> wrote:
> >
>
9 at 13:09, Richard Hauswald <
> richard.hausw...@googlemail.com> wrote:
>
>> Hello list,
>> as described in the Standard Directory Layout
>> (
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>> )
>> configuration
Is this a Maven question or an Eclipse (WTP) question? The subject says WTP
so I wonder what build path you're referring to.
/Anders
On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
richard.hausw...@googlemail.com> wrote:
> Hello list,
> as described in the Standard Directory
Hello list,
as described in the Standard Directory Layout
(http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
configuration files should be placed under src/main/config . But this
directory is not included in the build path. The directories
src/main
On 7/30/07, Dmitry <[EMAIL PROTECTED]> wrote:
> This means that by adopting Maven's standard conventions, we can package
> resources within JARs, simply by placing those resources in a standard
> directory structure. But when we put resources in standard directory we get
> nothing -what we did wro
We are suing common case which requires no changes to the POM project -
the packaging
of resources into a JAR file. Maven again uses for this task the standard
directory layout.
This means that by adopting Maven's standard conventions, we can package
resources within JARs, simp
D]
| > | Sent: Monday, January 15, 2007 5:47 AM
| > | To: users@maven.apache.org
| > | Subject: Standard directory layout
| > |
| > | Hello everybody,
| > |
| > | I need to define a specific Maven layout for the following
| > | application:
| > |
| > | The code is genera
nt: Monday, January 15, 2007 10:57 AM
| To: Maven Users List
| Subject: Re: Standard directory layout
|
| Maven 2.
| Is there any particular specification about that ?
|
|
| 2007/1/15, Ian Springer <[EMAIL PROTECTED]>:
| >
| > Are you using Maven 1 or Maven 2?
| >
| > | -Original M
he.org
| Subject: Standard directory layout
|
| Hello everybody,
|
| I need to define a specific Maven layout for the following
| application:
|
| The code is generated from an Uml modelling tool.
| It generates sources and xml files. The XML files are needed
| for the next tool that we are going to use.
|
Are you using Maven 1 or Maven 2?
| -Original Message-
| From: Fred Foucart [mailto:[EMAIL PROTECTED]
| Sent: Monday, January 15, 2007 5:47 AM
| To: users@maven.apache.org
| Subject: Standard directory layout
|
| Hello everybody,
|
| I need to define a specific Maven layout for the
Hi Fred,
I will try to answer your question by giving an exemple.
A typical maven directory structure for a project using modello (a source
generator tool) is :
- project
- src
- main
- java (here are the manually created java sources)
- mdo (here are the modello descriptors which
Hello everybody,
I need to define a specific Maven layout for the following application:
The code is generated from an Uml modelling tool.
It generates sources and xml files. The XML files are needed for the next
tool that we are going to use.
Our actual directory layout is like this:
-project
I put my images and javascript files etc directly into webapp. And
files which I use internally in my code go into src/main/resources. So
my personal usage seems to reflect that in the Spec.
Sounds like the documentation of m-war-p should probably be updated.
Wayne
On 1/12/07, Shelley L <[EMAIL
The sample usage example of the maven-war-plugin [1] demonstrates a war's
project structure with images in the src/main/resources directory, and a
resulting package structure with the images in web-inf/classes. According
to the Servlet 2.4 specification [2]:
"The WEB-INF node is not part of the
On 6/10/06, Max Cooper <[EMAIL PROTECTED]> wrote:
wolverine my wrote:
> The src/main/resources directory contains only the configurations
> which will be loaded by the classloader? So we really need to study
> the 3rd party library configurations to see if they are loaded via the
> classloader...
difference directories?
src/main/bin sounds reasonable. You'll probably need to (eventually)
consider how you want these files to end up in a build artifact, and
then how you are going to tell maven to find them.
-Max
I wish to see more tips and guides in the Maven standard directory
lay
start application or server, and
scripts for utilities (backup, housekeeping), and what do you think if
we save these scripts in /src/main/bin directory? Or do we save these
scripts into difference directories?
I wish to see more tips and guides in the Maven standard directory
layout description
ources that comprise your application's webapp.
-Max
wolverine my wrote:
Hi!
We have a plan to migrate from Ant to Maven in the future. Until then,
we would like to start our project using Ant but following the Maven's
standard directory layout (see
http://maven.apache.org/guides/in
Hi!
We have a plan to migrate from Ant to Maven in the future. Until then,
we would like to start our project using Ant but following the Maven's
standard directory layout (see
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html).
However, we
-the-standard-directory-layout.html
I have also found that even Maven does not
follow its own standard directory layout.
Thanks,
Jerry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
On 1/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
> For the most part I assume that what makes them standard is having a
> maven plugin (i.e. one that works out of the box without a prefix for
> definitions sake...) that uses said directory as a default. By that
> logic, src/main/webapp needs
/main/config/xdoclet
There is no property for Jalopy here because I use the jalopy.xml file with
the Jalopy plugin for Eclipse.
I hope that helps.
-- Chuck
On 1/11/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
> I've got a few questions on the "Standard Directory Layou
I've got a few questions on the "Standard Directory Layout" described here:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
For the most part I assume that what makes them standard is having a
maven plugin (i.e. one that works out of
fully assume your message belongs to the previous thread and
display it threre, which is quite annoying for people using this
feature.
Thanks,
-Ralph.
On 02.01.2006, at 06:17, Man-Chi Leung wrote:
hi,
just a very coffee-like question!
as maven community encourages standard directory layout,
Ralph.
On 02.01.2006, at 06:17, Man-Chi Leung wrote:
hi,
just a very coffee-like question!
as maven community encourages standard directory layout, I am very
curious on the convention for aspectj files
1) /src/aspect
2) /src/main/aspect
3) /src/main/resources/aspect
I opted for number 2
a
hi,
just a very coffee-like question!
as maven community encourages standard directory layout, I am very
curious on the convention for aspectj files
1) /src/aspect
2) /src/main/aspect
3) /src/main/resources/aspect
I opted for number 2
anyone can share with me your convention?
Regards
Ashley Williams [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 15, 2005 1:51 PM
To: Maven Users List
Subject: Re: [m2] Standard directory layout for generated sources
Hi John,
Any reason why each plugin has to generate its sources into
its own plugin-prefix root directory?
After all as I add cl
Maven Users List
> Subject: Re: [m2] Standard directory layout for generated sources
>
> Hi John,
>
> Any reason why each plugin has to generate its sources into
> its own plugin-prefix root directory?
> After all as I add class after class and package after
> package int
ave its own generated directory and inform it to Maven.
Despite I still think it would be great to have a standard
directory layout for generated files.
Regards,
Dário
-Original Message-
From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 14 de dezembro de 2005 09:32
To
Hi John,
Thanks a lot. I appreciated it.
I was wondering if this could be documented in the "Introduction to the
Standard Directory Layout" and/or "Plug-in Development Guide" sections. This
way plugin developers would have an idea of the standard layout for generated
code
gin could tell Maven on the fly about the existence of a
new source directory ? If this is possible, then a plugin could have its own
generated directory and inform it to Maven. Despite I still think it would be
great to have a standard directory layout for generated files.
Regards,
Dário
-
could have its own
generated directory and inform it to Maven. Despite I still think it would be
great to have a standard directory layout for generated files.
Regards,
Dário
-Original Message-
From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 14 de dezembro de 2005 09
On 12/14/05, Dário Luís Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
> When looking at the standard layout directory, I thought it would be great to
> have a common directory for the generated sources also since Maven already
> has a generate-sources lifecycle phase. This way we don´t need to t
Hi there,
When looking at the standard layout directory, I thought it would be great to
have a common directory for the generated sources also since Maven already has
a generate-sources lifecycle phase. This way we don´t need to tell the compiler
where to find the generated sources.
Please let
I am confused by the difference between the doc and the wiki.
http://maven.apache.org/reference/dirlayout.html
http://wiki.codehaus.org/maven/DirectoryLayout
E.g. src/java vs src/main/java
What will be the future?
Is m1 1.1 or m2 going to adopt the wiki's recommended layout?
J
-
45 matches
Mail list logo
