You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Susheel Jalali <Su...@Coscend.com> on 2016/02/02 08:08:44 UTC
Re: Jira Issue created: Current maven build does not create the
source artifact
Dear Maxim,
This is regarding compiling 3.1.0 from source code
(https://issues.apache.org/jira/browse/OPENMEETINGS-1302).Thank you for
resolving that issue/task.
Upon compilation of source code
(apache-openmeetings-3.1.0-SNAPSHOT-src.zip
<https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/artifact/openmeetings-server/target/apache-openmeetings-3.1.0-SNAPSHOT-src.zip>)from
the link below, we are getting a different tree structure from that of
the binary (apache-openmeetings-3.1.0-SNAPSHOT.tar.gz
<https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/artifact/openmeetings-server/target/apache-openmeetings-3.1.0-SNAPSHOT.tar.gz>)
uploaded in the link:
https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/?
We used ‘mvn clean install’, as the source has pom.xml (instead of ant
with build.xml), what else is different in the process of compilation of
3.1.0 versus 3.0.7?
-----------------
Tree structure in
The binary downloaded from OpenMeetings site:
|- conf
|- lib
|- plugins
|- webapps
|- openmeetings
|- conf
|- css
|- default
|- docs
|- images
|- js
|- languages
|- public
|- screenshare
|- streams
|- upload
|- WEB-INF
|- root
Our compiled version:
|-- openmeetings-core
src
target
|-- openmeetings-db
src
target
|-- openmeetings-flash
src
target
|-- openmeetings-install
src
target
|-- openmeetings-screenshare
src
target
|-- openmeetings-server
src
target
|-- openmeetings-service
src
target
|-- openmeetings-util
src
target
|-- openmeetings-web
|- src
|- target
|- test-data
|-- openmeetings-webservice
|- target
|- maven-shared-archive-resources
|- site
|- css
|- images
[] apache-openmeetings-3.1.0-SNAPSHOT-src.tar.gz
[] CHANGELOG
[] LICENSE
[] NOTICE
[] pom.xml
[] README
Attached are picture of the two directory structures.
-- Binary tree structure downloaded from OpenMeetings
site:Binary_Directories.png
-- Our compiled tree structure:Compiled_Directories.png
Thank you.
-- --
Sincerely,
Susheel Jalali
Coscend Communications Solutions
www.Coscend.com
----------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
Messages from Coscend Communications Solutions' posted at:
http://www.Coscend.com/Terms_and_Conditions.html
Thanks
will address it until next release
On Thu, Dec 17, 2015 at 8:22 PM, Susheel Jalali<Su...@coscend.com>
wrote:
Dear Maxim and Sebastian,
We have created Jira Issue for 310 source code:
https://issues.apache.org/jira/browse/OPENMEETINGS-1302
Current maven build does not create the source artifact.
--
Regards,
Susheel Jalali
Coscend Communications Solutions
Web site:<http://www.coscend.com/>www.Coscend.com
------------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
Messages from Coscend Communications Solutions' posted at: <
http://www.coscendcommunications.com/Terms_and_Conditions.html>
http://www.Coscend.com/Terms_and_Conditions.html
Re: Jira Issue created: Current maven build does not create the
source artifact
Posted by Maxim Solodovnik <so...@gmail.com>.
There is no issue here, binary artifacts are located under
openmeetings-server/target folder
WBR, Maxim
(from mobile, sorry for the typos)
On Feb 2, 2016 13:12, "Susheel Jalali" <Su...@coscend.com> wrote:
> Dear Maxim,
>
> This is regarding compiling 3.1.0 from source code (
> https://issues.apache.org/jira/browse/OPENMEETINGS-1302). Thank you for
> resolving that issue/task.
>
> Upon compilation of source code (
> apache-openmeetings-3.1.0-SNAPSHOT-src.zip
> <https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/artifact/openmeetings-server/target/apache-openmeetings-3.1.0-SNAPSHOT-src.zip>
> ) from the link below, we are getting a different tree structure from
> that of the binary (apache-openmeetings-3.1.0-SNAPSHOT.tar.gz
> <https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/artifact/openmeetings-server/target/apache-openmeetings-3.1.0-SNAPSHOT.tar.gz>)
> uploaded in the link:
>
>
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/lastBuild/
> ?
>
> We used ‘mvn clean install’, as the source has pom.xml (instead of ant
> with build.xml), what else is different in the process of compilation of
> 3.1.0 versus 3.0.7?
>
> -----------------
>
> Tree structure in
>
> The binary downloaded from OpenMeetings site:
>
> |- conf
> |- lib
> |- plugins
> |- webapps
> |- openmeetings
> |- conf
> |- css
> |- default
> |- docs
> |- images
> |- js
> |- languages
> |- public
> |- screenshare
> |- streams
> |- upload
> |- WEB-INF
> |- root
>
> Our compiled version:
> |-- openmeetings-core
> src
> target
> |-- openmeetings-db
> src
> target
> |-- openmeetings-flash
> src
> target
> |-- openmeetings-install
> src
> target
> |-- openmeetings-screenshare
> src
> target
> |-- openmeetings-server
> src
> target
> |-- openmeetings-service
> src
> target
> |-- openmeetings-util
> src
> target
> |-- openmeetings-web
> |- src
> |- target
> |- test-data
> |-- openmeetings-webservice
> |- target
> |- maven-shared-archive-resources
> |- site
> |- css
> |- images
> [] apache-openmeetings-3.1.0-SNAPSHOT-src.tar.gz
> [] CHANGELOG
> [] LICENSE
> [] NOTICE
> [] pom.xml
> [] README
>
> Attached are picture of the two directory structures.
> -- Binary tree structure downloaded from OpenMeetings site:
> Binary_Directories.png
> -- Our compiled tree structure: Compiled_Directories.png
> Thank you.
>
> -- --
> Sincerely,
>
> Susheel Jalali
> Coscend Communications Solutions
> www.Coscend.com
> ----------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
> Messages from Coscend Communications Solutions' posted at:
> http://www.Coscend.com/Terms_and_Conditions.html
>
> Thanks
> will address it until next release
>
> On Thu, Dec 17, 2015 at 8:22 PM, Susheel Jalali <Su...@coscend.com> <Su...@coscend.com>
> wrote:
>
>
> Dear Maxim and Sebastian,
>
> We have created Jira Issue for 310 source code:
> https://issues.apache.org/jira/browse/OPENMEETINGS-1302
> Current maven build does not create the source artifact.
>
> --
>
> Regards,
>
> Susheel Jalali
>
> Coscend Communications Solutions
> Web site:<http://www.coscend.com/> <http://www.coscend.com/>www.Coscend.com
>
> ------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
> Messages from Coscend Communications Solutions' posted at: <http://www.coscendcommunications.com/Terms_and_Conditions.html>http://www.Coscend.com/Terms_and_Conditions.html
>
>
>