Yes,
you're right. Not a so heavy issue.
Just a correctness remark.
I've already filed a jira issue for it with simple project test case.
Regards,
Patrizio
[EMAIL PROTECTED] wrote:
It doesn't surprise me too much that the maven-jar-plugin still creates
empty directories even when all files
It doesn't surprise me too much that the maven-jar-plugin still creates
empty directories even when all files that were in that directory have
been excluded. I haven't checked myself, but it sounds like a situation
that the plugin author could easily have overlooked.
But it doesn't cause any probl
Thanks for your answer,
so is it a real problem...?
Thanks
Olivier Lamy wrote:
Post an issue in jira.
And attach a simple project test case to reproduce the issue.
Thanks,
--
Olivier
2008/3/11, Patrizio Munzi <[EMAIL PROTECTED]>:
Hi All,
I'm trying to exclude some files from the built
Post an issue in jira.
And attach a simple project test case to reproduce the issue.
Thanks,
--
Olivier
2008/3/11, Patrizio Munzi <[EMAIL PROTECTED]>:
> Hi All,
>
> I'm trying to exclude some files from the built jar by using the
> maven-jar-plugin exclude feature.
>
> Here's my configuration:
Hi All,
I'm trying to exclude some files from the built jar by using the
maven-jar-plugin exclude feature.
Here's my configuration:
**/*.properties
**/*.xml
**/*.xsd
Although all the specified files are actually excluded from the deployed
jar, the directory paths of the excluded fil
Hi All,
I'm trying to exclude some files from the built jar by using the
maven-jar-plugin exclude feature.
Here's my configuration:
**/*.properties
**/*.xml
**/*.xsd
Although all the specified files are actually excluded from the deployed
jar, the directory paths of the excluded
thanks for your Olivier ,
it works now!
i forgot to make a clean in the target folder so that's why the files
were always present !
regards
The excludes field in the jar plugin is to exclude content from
${project.build.outputDirectory} not to exclude resources.
In order to exclude resources
The excludes field in the jar plugin is to exclude content from
${project.build.outputDirectory} not to exclude resources.
In order to exclude resources have a look here [1].
I don't really understand your jar plugin configuration.
Can you try a more simple :
org.apache.maven.plugi
Thanks Olivier (and Jochen and Dennis),
it is now building without any error but the xsd files is always here
i'm gonna try with Ant task to if it is working !
regards
Hi,
Can you try with :
**/*.xsd
--
Olivier
2008/1/12, supareno <[EMAIL PROTECTED]>:
Hel
The excludes configuration is a set of things to exclude. It needs to be
configured like this:
**/*.xsd
supareno wrote:
Hello guys
i read the previous threads about exclusion with interest
because i am always confronted with the "excludes" problem
i followed all the steps:
changed my se
On Jan 12, 2008 3:59 PM, supareno <[EMAIL PROTECTED]> wrote:
> [INFO] Failed to configure plugin parameters for:
> org.apache.maven.plugins:maven-jar-plugin:2.2-SNAPSHOT
>
> (found static expression: '**/*.xsd' which may act as a default value).
Configuration problem on your side, use
Hi,
Can you try with :
**/*.xsd
--
Olivier
2008/1/12, supareno <[EMAIL PROTECTED]>:
> Hello guys
>
> i read the previous threads about exclusion with interest
> because i am always confronted with the "excludes" problem
>
> i followed all the steps:
> changed my
Hello guys
i read the previous threads about exclusion with interest
because i am always confronted with the "excludes" problem
i followed all the steps:
changed my settings.xml to enable snapshot plugin repositories...
(http://maven.apache.org/guides/development/guide-plugin-snapshot-repositori
Hi,
Sorry for incomplete information about the problem. I used task ,
and it is working now.
Did not try the snapshot jar plugin yet.
Thanks and regards,
Amit Kumar
On Jan 11, 2008 5:46 AM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I don't think Simon is telling you to use Ant's jar command -- ins
I don't think Simon is telling you to use Ant's jar command -- instead
he is suggesting that you use Ant's task to physically remove
the unwanted files out of /target/ before allowing Maven to do its own
packaging step. (Right, Simon?) You would probably want to bind this
to prepare-package as you
Hi Simon,
Being totally unaware of ANT although I tried but of no use.
I used this with google's help
maven-antrun-plugin
prepare-package
Nothing to patch locally.
The snapshot with this patch is available in snapshot plugin repositories.
In order to test this have a look here [1] (first section "How to
include the plugin snapshot repositories as part of your build").
If you have any issues let us know,
Thanks,
--
Olivier
[1]
htt
Hi,
I have downloaded the patches from the link mentioned by you. But I don't
know how to apply them.
regards,
Amit
On Jan 10, 2008 6:29 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> No you don't miss something here.
> It's a know issue [1] and it's fixed in trunk.
> You can try last snaps
amit kumar <[EMAIL PROTECTED]> schrieb:
> Just like WAR can I as well exclude some files from JAR builds as well?
Not until the next version of the jar plugin is released.
For the moment, the usual workaround is to use the antrun plugin to remove the
unwanted files before the jar is created
Hi,
No you don't miss something here.
It's a know issue [1] and it's fixed in trunk.
You can try last snapshot to test the fix.
--
Olivier
[1] http://jira.codehaus.org/browse/MJAR-30
2008/1/10, amit kumar <[EMAIL PROTECTED]>:
> HI,
> Just like WAR can I as well exclude some files from JAR builds
HI,
Just like WAR can I as well exclude some files from JAR builds as well?
I have used this, but not working.
org.apache.maven.plugins
maven-jar-plugin
2.1
jar
**/*.xsd
src/schema/xsd
Am I mis
21 matches
Mail list logo
