You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Aaron.Dossett" <Aa...@target.com> on 2015/09/01 03:51:45 UTC

Atlas build

Hello,

It has been a few months since I have been in the Atlas code base, but looking forward to getting reacquainted with it.

I cloned the repo today (via github) and tried to build the code per instructions in InstallationSteps.twiki but `mvn clean install` fails with this error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on project apache-atlas: Failed to create assembly: Error adding file to archive: /myhomedir/apache/atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war isn't a file. -> [Help 1]

Is `mvn clean install` still the correct first build step?  I see that the assembly plugin is using the `single` goal now, which is good.  In another project I worked on, the assembly step had to be moved into its own module to get the maven dependencies to work correctly when moving to assembly:single.  Apache Knox also does something like this, and it’s a very clean structure.

Is there another way I should be building Atlas?  Would moving the assembly step into its own module be helpful?  If so I can open a JIRA and work on that.

Best, Aaron

Re: Atlas build

Posted by Seetharam Venkatesh <ve...@innerzeal.com>.
Aaron, looks like a regression. Please create a blocker jira and we will
look into it. assembly:assembly should work as well.

On Mon, Aug 31, 2015 at 6:55 PM John Speidel <js...@hortonworks.com>
wrote:

> Yeah, that is a know issue.  Simply creating an empty war file before the
> build will allow the build to succeed.
>
> -John
>
> Sent from my iPad
>
> > On Aug 31, 2015, at 9:51 PM, Aaron.Dossett <Aa...@target.com>
> wrote:
> >
> > Hello,
> >
> > It has been a few months since I have been in the Atlas code base, but
> looking forward to getting reacquainted with it.
> >
> > I cloned the repo today (via github) and tried to build the code per
> instructions in InstallationSteps.twiki but `mvn clean install` fails with
> this error:
> >
> > [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on
> project apache-atlas: Failed to create assembly: Error adding file to
> archive:
> /myhomedir/apache/atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war
> isn't a file. -> [Help 1]
> >
> > Is `mvn clean install` still the correct first build step?  I see that
> the assembly plugin is using the `single` goal now, which is good.  In
> another project I worked on, the assembly step had to be moved into its own
> module to get the maven dependencies to work correctly when moving to
> assembly:single.  Apache Knox also does something like this, and it’s a
> very clean structure.
> >
> > Is there another way I should be building Atlas?  Would moving the
> assembly step into its own module be helpful?  If so I can open a JIRA and
> work on that.
> >
> > Best, Aaron
>

Re: Atlas build

Posted by John Speidel <js...@hortonworks.com>.
Yeah, that is a know issue.  Simply creating an empty war file before the build will allow the build to succeed.

-John

Sent from my iPad

> On Aug 31, 2015, at 9:51 PM, Aaron.Dossett <Aa...@target.com> wrote:
> 
> Hello,
> 
> It has been a few months since I have been in the Atlas code base, but looking forward to getting reacquainted with it.
> 
> I cloned the repo today (via github) and tried to build the code per instructions in InstallationSteps.twiki but `mvn clean install` fails with this error:
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on project apache-atlas: Failed to create assembly: Error adding file to archive: /myhomedir/apache/atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war isn't a file. -> [Help 1]
> 
> Is `mvn clean install` still the correct first build step?  I see that the assembly plugin is using the `single` goal now, which is good.  In another project I worked on, the assembly step had to be moved into its own module to get the maven dependencies to work correctly when moving to assembly:single.  Apache Knox also does something like this, and it’s a very clean structure.
> 
> Is there another way I should be building Atlas?  Would moving the assembly step into its own module be helpful?  If so I can open a JIRA and work on that.
> 
> Best, Aaron