logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Deboy <scott.de...@gmail.com>
Subject Re: companions parent relative path
Date Thu, 18 Aug 2011 06:18:04 GMT
For some reason, my mac build still has the issues mentioned below.

Christian, do you see the same thing?  A problem with component?

Thanks

Scott

On Wed, Aug 17, 2011 at 10:33 PM, Scott Deboy <scott.deboy@gmail.com> wrote:

> After my latest commit, I was able to checkout and build on a clean windows
> box without bypassing tests...so I'm nuking my .m2 repo folder and
> rebuilding on the Mac..hopefully the build will work fine (and the test
> issue will just go away).
>
> Scott
>
>
> On Wed, Aug 17, 2011 at 6:59 PM, Scott Deboy <scott.deboy@gmail.com>wrote:
>
>> I just committed a fix to get assembly plugin to work for me (needed
>> 2.2.x).  I can build and install the packages but I get an error running
>> assembly:single for the companions parent, even though I have installed
>> component..here's the error:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default-cli) on
>> project apache-log4j-companions-parent: Failed to create assembly: Artifact:
>> log4j:apache-log4j-component:jar:1.0-SNAPSHOT (included by module) does not
>> have an artifact with a file. Please ensure the package phase is run before
>> the assembly is generated. -> [Help 1]
>>
>> Thoughts?
>>
>>
>> On Wed, Aug 17, 2011 at 9:30 AM, Christian Grobmeier <grobmeier@gmail.com
>> > wrote:
>>
>>> I have fixed the situation with this information:
>>>
>>> http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
>>>
>>> Now parent has got some kind of multimodule assembly. Using mvn
>>> assembly:single in parent will cause to assemble all modules. I could
>>> not inspect the final result b/c of test errors - we need to check it
>>> later
>>>
>>> In addition it is possible to make a single assembly of each
>>> companion, like for example component, on each own. Just cd to the
>>> component directory and type "mvn assembly:single" as you always did
>>>
>>> For me it worked all well and it created a nice bunch of files :-)
>>>
>>> Cheers
>>>
>>> On Wed, Aug 17, 2011 at 4:27 PM, Scott Deboy <scott.deboy@gmail.com>
>>> wrote:
>>> > If you could make whatever changes you feel are appropriate, that would
>>> be
>>> > great.
>>> >
>>> > Scott
>>> >
>>> >
>>> >
>>> > On Aug 17, 2011, at 2:31 AM, Christian Grobmeier <grobmeier@gmail.com>
>>> > wrote:
>>> >
>>> >> yes, I have move the assembly plugin from subprojects to parent.
>>> >> But of course, the parent does not have src/assembly/bin.xml
>>> >> So either we create that file or we move the assemblyplugin config
>>> >> back to the submodules
>>> >>
>>> >> It does not make sense to use assembly for parent, I think it would
be
>>> >> best to move it back
>>> >>
>>> >> Sorry for the trouble, I tried to clean up as much as possible and
>>> >> want to get everything working agian until release
>>> >>
>>> >> Do you move it or shall i?
>>> >>
>>> >> On Wed, Aug 17, 2011 at 10:47 AM, Scott Deboy <scott.deboy@gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> Having issues building, related to src/assembly/bin.xml in
>>> >>> companions-parent..
>>> >>>
>>> >>> Installing receivers gives me an error about companions parent:
>>> >>> Failed to read artifact descriptor for
>>> >>> log4j:apache-log4j-component:jar:1.0-SNAPSHOT: Could not find
>>> artifact
>>> >>> log4j:apache-log4j-companions-parent:pom:1.0-SNAPSHOT -> [Help
1]
>>> >>>
>>> >>> So I tried to install in companions parent and got an error that
>>> bin.xml
>>> >>> didn't exit.
>>> >>>
>>> >>> Ideas?
>>> >>>
>>> >>>
>>> >>> On Wed, Aug 17, 2011 at 1:11 AM, Christian Grobmeier
>>> >>> <grobmeier@gmail.com>
>>> >>> wrote:
>>> >>>>
>>> >>>> I had it from here:
>>> >>>>
>>> >>>>
>>> >>>>
>>> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Example_2
>>> >>>> and it worked for me on my Mac.
>>> >>>>
>>> >>>> But I just tried it with your version, it works too so we can
use
>>> that
>>> >>>> one.
>>> >>>>
>>> >>>> Not sure why they have ... on their site. Maybe a typo?
>>> >>>>
>>> >>>> Cheers
>>> >>>>
>>> >>>> On Wed, Aug 17, 2011 at 9:58 AM, Scott Deboy <scott.deboy@gmail.com
>>> >
>>> >>>> wrote:
>>> >>>>>
>>> >>>>> I see a relative path for each of the companions to the
companions
>>> >>>>> parent
>>> >>>>> folder is prefixed with three dots.  That didn't work for
me on the
>>> >>>>> Mac,
>>> >>>>> I
>>> >>>>> had to change it to
>>> >>>>>
>>>  <relativePath>../apache-log4j-companions-parent</relativePath>
>>> >>>>>
>>> >>>>> I hope that's ok, was about to commit a fix for that.
>>> >>>>>
>>> >>>>> Scott
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> http://www.grobmeier.de
>>> >>>>
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >>>>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> http://www.grobmeier.de
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>>
>>
>

Mime
View raw message