You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Rob Oxspring <ro...@imapmail.org> on 2004/04/09 15:29:44 UTC
[all] maven build - help required
I've freshly set up my environment to do some work on commons-cli
(RESEARCH_CLI_2_ROXSPRING branch if that matters) and am really
struggling to get the build working.
Using a clean checkout of jakarta-commons, running maven (rc1) from the
cli directory ends up failing to compile any of the java source
(although maven claims a successful build):
java:compile:
[echo] Compiling to
C:\Java\apache.org\jakarta-commons\cli/target/classes
[echo] No java source files to compile.
I tried a few other components at random and founnd that while codec,
collections and digester do the same; validator claims to be compiling
20 file.
Could anyone enlighten me as to what's gone wrong? is it my set up? is
it the new commons-build? is it just general maven black magic?
Thanks,
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] maven build - help required
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
This could be verflow from both the commons-build efforts and past
changes to the /cli/project.xml file.
I notice that back in March you made some changes to the build section,
then it looks like I removed it when we started extending the
commons-build/project.xml, which may have been unintended. I recommend
we comment out the extend and add this back in as a test.
<build>
<resources>
<resource>
<directory>src/java/org/apache/commons/cli2</directory>
<targetPath>org/apache/commons/cli2</targetPath>
<includes>
<include>**/*.properties</include>
</includes>
</resource>
</resources>
<!-- Unit test classes -->
<unitTest>
<includes>
<include>**/*Test.java</include>
</includes>
</unitTest>
</build>
-Mark
David Graham wrote:
>--- Rob Oxspring <ro...@imapmail.org> wrote:
>
>
>>I've freshly set up my environment to do some work on commons-cli
>>(RESEARCH_CLI_2_ROXSPRING branch if that matters) and am really
>>struggling to get the build working.
>>
>>Using a clean checkout of jakarta-commons, running maven (rc1) from the
>>cli directory ends up failing to compile any of the java source
>>(although maven claims a successful build):
>>
>>java:compile:
>> [echo] Compiling to
>>C:\Java\apache.org\jakarta-commons\cli/target/classes
>> [echo] No java source files to compile.
>>
>>
>
>It sounds like your <build> element in project.xml isn't configured
>correctly. Take a look at the setup for working components to see what
>you're missing.
>
>David
>
>
>
>>I tried a few other components at random and founnd that while codec,
>>collections and digester do the same; validator claims to be compiling
>>20 file.
>>
>>Could anyone enlighten me as to what's gone wrong? is it my set up? is
>>it the new commons-build? is it just general maven black magic?
>>
>>Thanks,
>>
>>Rob
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] maven build - help required
Posted by David Graham <gr...@yahoo.com>.
--- Rob Oxspring <ro...@imapmail.org> wrote:
> I've freshly set up my environment to do some work on commons-cli
> (RESEARCH_CLI_2_ROXSPRING branch if that matters) and am really
> struggling to get the build working.
>
> Using a clean checkout of jakarta-commons, running maven (rc1) from the
> cli directory ends up failing to compile any of the java source
> (although maven claims a successful build):
>
> java:compile:
> [echo] Compiling to
> C:\Java\apache.org\jakarta-commons\cli/target/classes
> [echo] No java source files to compile.
It sounds like your <build> element in project.xml isn't configured
correctly. Take a look at the setup for working components to see what
you're missing.
David
>
> I tried a few other components at random and founnd that while codec,
> collections and digester do the same; validator claims to be compiling
> 20 file.
>
> Could anyone enlighten me as to what's gone wrong? is it my set up? is
> it the new commons-build? is it just general maven black magic?
>
> Thanks,
>
> Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org